from_file

Target database: Snowflake, Azure SQL Database

Resolved as the source file path in file load execution.

See also:

• OVERRIDE_FILE_LOAD

• from_path

• Variables

Notes

Supported in file loads.

Bucket/container address is stripped from the file path.

Examples

Snowflake: Variable used in OVERRIDE_FILE_LOAD

Manifest

<from_file> is resolved as the manifest path without bucket/container address, for example:

manifest/ratecode_description/manifest-table.ratecode_description.1619681245.batch.1619681245640.fullscanned.false.skiph.1.delim.comma.csv.gz.json

Note that the manifest path is not useful in file loading terms in the Snowflake context. Therefore, <from_file> should be used with Snowflake in manifest loads only for metadata purposes.

Single file load

<from_file> is resolved as the source file path without bucket/container address, for example:

ratecode_description/table.ratecode_description.1619598629.batch.1619598629291.fullscanned.false.skiph.1.delim.comma.csv.gz

Azure SQL Database: Variable used in OVERRIDE_FILE_LOAD

<from_file> is similar to <from_path>, only the single quotes are omitted. See Azure SQL Database examples in <from_path>.

Manifest

File queued with a manifest:

taxidata1/ratecode_description.batch.1618916378963.csv

<from_file> is resolved as a file path in a manifest entry, for example:

taxidata1/ratecode_description.batch.1618916378963.csv

Single file load

File queued:

azure://example.blob.core.windows.net/example-container/taxidata1/ratecode_description.1619598629.batch.1619598629291.fullscanned.false.skiph.1.delim.comma.csv

<from_file> is resolved as the file path without the bucket/container address:

taxidata1/ratecode_description.1619598629.batch.1619598629291.fullscanned.false.skiph.1.delim.comma.csv