Input 

Document

• Min: 1

• Max: 1

• ELT Select

• ELT Intersect

The SQL query which you want to transform.

Output

Document

• Min: 1

• Max: 1

• ELT Insert-Select

• ELT Unique

• ELT Limit

The outgoing SQL query with the specified transformation. 

Error

Error handling is to have a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that might arise while running the Pipeline by choosing one of the options from the When errors occur section under the Views tab.

The options available are:

• Stop Pipeline Execution: Stops the current pipeline execution when an error arises.

• Discard Error Data and Continue: Ignores an error completely, discard that record, and continue with the rest of the records.

• Route Error Data to Error View: Routes the data to an error view of the Snap and then decides what to do with the error.

See Error View in Pipeline in examples to understand the Snap error view settings and error output. For more information on the error view and handling error output in a Pipeline, see Error handling in Pipelines.

Label*

String

The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your Pipeline.

Default Value: ELT Cast Function
Example: CastFunctions_Testing

Get preview data

Checkbox

Select this checkbox to include a preview of the query's output. The Snap performs limited execution and generates a data preview during Pipeline validation.

The number of records displayed in the preview (upon validation) is the smaller of the following:

• Number of records available upon execution of the SQL query generated by the Snap.

• The value set in the Preview Data Count setting (default is 50 records).

Rendering Complex Data Types in Databricks Lakehouse Platform

Pass through

Checkbox

Select this checkbox to specify that the Snap must include the incoming document (SQL query) in its output document.

Default Value: Not selected
Example: Selected

Cast functions

Specify your SQL expressions, data type and the relevant alias using this fieldset. Click to add a new row. Ensure that you specify each expression in a separate row.

Function*

String/Expression

Specify your function/operation to be performed in the specified columns. Ensure that you specify each function in a separate row.

Data Type*

String/Expression

Specify the data type for the selected expression/function. Clickto retrieve the list of the supported aggregate functions. This is typically a column name in your source table. Each of the function needs only one value.
Default Value: None.
Example: ORDER_ID

Alias*

String

Specify the column in which the result of the binary function has to be displayed. You can also reference this name in downstream Snaps to process the data further. 

Default Value: None.
Example: A_ORDIDS

Missing property value

You have not specified a value for the mandatory field where this message is displayed.

Ensure that you specify appropriate values for all mandatory fields in the Snap configuration.

Invalid placement of ELT Cast Function snap

ELT Cast Function Snap cannot be used at the start of a Pipeline.

Move the ELT Cast Function Snap to either the middle or the end of the Pipeline.

CAST (DEPT AS BINARY) is not a natural function for Snowflake. It displays the following error message. net.snowflake.client.jdbc.SnowflakeSQLException: The following string is not a legal hex-encoded value: 'operat'
(CDW: Snowflake)

In the SQL query, SELECT CAST(DEPT AS BINARY) AS dept_binary FROM BIGDATAQA.TEST_DATA.org10, CAST (DEPT AS BINARY) is not a natural function for Snowflake.

Instead of (DEPT AS BINARY), you can use:

• to_binary

• as_binary

Examples:

1. insert into TEST_DATA.demo_binary_hex (b) select to_binary(hex_encode('LOGO'), 'HEX');
   
   

2. select as_binary(binary1) as "Binary" from TEST_DATA.type_as_binary;