target_entity_attribute_list

Target database: Snowflake, Azure Synapse SQL, Microsoft Fabric, Google BigQuery, Databricks SQL

Resolved as a comma-separated list of target entity attributes in load execution.

See also:

Variables

Usage

VARIABLE

<target_entity_attribute_list>

Notes

Supported in all loads.

For file loads, the list can be specified in the manifest columns property (SaaS, Private).

Examples

Snowflake: Variable used in OVERRIDE_FILE_LOAD

<target_entity_attribute_list> is resolved as a comma-separated list of attributes defined in a manifest, for example:

ratecodeid, description

File load customized with OVERRIDE_FILE_LOAD:

SQL

COPY INTO ...
(<target_entity_attribute_list>)
FROM ...
...
;

File load executed in Snowflake:

SQL

COPY INTO ...
(ratecodeid, description)
FROM ...
...
;

Azure Synapse SQL and Microsoft Fabric: Variable used in OVERRIDE_FILE_LOAD

<target_entity_attribute_list> is resolved as a comma-separated list of attributes in parentheses defined in a manifest, for example:

(ratecodeid, description)

File load customized with OVERRIDE_FILE_LOAD:

SQL

COPY INTO ...
<target_entity_attribute_list>
FROM ...
WITH (...);

File load executed in Azure Synapse SQL:

SQL

COPY INTO ...
(ratecodeid, description)
FROM ...
WITH (...);

Databricks SQL: Variable used in OVERRIDE_FILE_LOAD

<target_entity_attribute_list> is resolved as a comma-separated list of attributes in parentheses defined in a manifest, for example:

(ratecodeid, description)

Notice that in Databricks case the read data is tried to be casted to match the target entity.

File load customized with OVERRIDE_FILE_LOAD:

SQL

COPY INTO ...
FROM (SELECT <target_entity_attribute_list> FROM <from_path>)
WITH (...);

File load executed in Azure Synapse SQL:

SQL

COPY INTO ...
FROM (SELECT CAST(_c0 AS INTEGER) AS ratecodeid, _c1 AS description 
     FROM 'abfss://data@example.blob.core.windows.net/example-container/taxidata/'
)
WITH (...);

Google BigQuery: Variable used in OVERRIDE_FILE_LOAD

<target_entity_attribute_list> is resolved as a comma-separated list of attributes in parentheses defined in a manifest, for example:

(ratecodeid, description)

File load customized with OVERRIDE_FILE_LOAD:

SQL

LOAD DATA INTO ...
<target_entity_attribute_list> 
FROM ...

File load executed in Azure Synapse SQL:

SQL

LOAD DATA ...
(ratecodeid INT64, description STRING)
FROM ...