location_column - Advanced SQL Engine - Teradata Database

SQL Data Definition Language Syntax and Examples

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Published
July 2021
Language
English (United States)
Last Update
2021-07-27
dita:mapPath
spp1591731285373.ditamap
dita:ditavalPath
spp1591731285373.ditaval
dita:id
B035-1144
lifecycle
previous
Product Category
Teradata Vantage™

[Optional] Specify a column that has this definition:

Location VARCHAR(2048) CHARACTER SET UNICODE CASESPECIFIC

The location_column and the payload_column or data_column_definition fields are optional, because NOS generates them. For CSV, if NOS is cannot generate the columns, it generates the payload column of DATASET CSV instead.

The Payload column type of the generated location column depends on extension of files in location path:

FIle Extension Payload Column Type
.json or .json.gz JSON
.csv or .csv.gz DATASET STORAGE FORMAT CSV
No file extension or unrecognized file extension JSON, with unsupported file type warning
mixed .json and .csv files at the location path Based on the type of the first valid file Vantage encounters. Subsequent files from the location that have different extensions are ignored.

For this reason, it is best to specify a payload column for a location that has mixed format data, if you cannot arrange to have only one data format at the specified LOCATION.

If you specify location_column, you must specify it first.

For information about NOS, see Teradata Vantage™ - Native Object Store Getting Started Guide, B035-1214.