15.10 - metadata - Teradata Database

Teradata Database Teradata JSON

prodname
Teradata Database
vrm_release
15.10
created_date
December 2015
category
Programming Reference
featnum
B035-1150-151K
The following describes the metadata variables.
All literals must be lowercase.
"metadata" :
Required, literal entry.
Must be lowercase.
"operation" :
Required, literal entry.
"insert" | "update" | "merge" | "delete"
Operation to perform.
In a MERGE operation, the target table must have a primary index, and the primary index has to be a member of the keys in the metadata.
"keys":
Using keys is optional. If used, "keys": is a required, literal entry.
All names given in the keys clause must be present in the column assignment clause.
The keys are used to perform the join between the temporary table created by the row and column expressions and the target table. This should be used carefully as it can drastically affect performance. In the case of a MERGE operation, the target table must have a primary index, and the primary index has to be a member of the specified keys.
"table_column_name"
The name of any column in the table referenced by table_name. The user invoking JSON_SHRED_BATCH must have the required privileges (INSERT, UPDATE, and so forth) on this existing table. table_name is specified in the table expression of JSON_SHRED_BATCH.
"filter":
Filtering is optional. If used, "filter": is a required, literal entry.
filter_expression
SQL statement referencing elements of the column or query expressions.
Example filter statement: "filter" : "empId<5000"