Differences between JSON_TABLE and TD_JSONSHRED - Teradata VantageCloud Lake

Lake - Working with SQL

Deployment
VantageCloud
Edition
Lake
Product
Teradata VantageCloud Lake
Release Number
Published
February 2025
ft:locale
en-US
ft:lastEdition
2025-11-21
dita:mapPath
jbe1714339405530.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
jbe1714339405530
Feature JSON_TABLE TD_JSONSHRED
Speed Slower Faster
Supports CLOB data type for input and output data No

16 MB (JSON data type maximum size) limit on input. Limits on output determined by data type.

Yes

CLOB type (2 GB maximum size) allowed for input/output and other data types

Case Sensitive string matching Always Optional
JSONPath support Yes No
Return data types More Fewer

Can output as VARCHAR or CLOB and cast to other types

Pass-through columns (columns that do not contain JSON data in the input table) Appear after shredded JSON data in returned table Appear before shredded JSON data in the returned table
Handling of oversized shredded string data Truncates shredded JSON data that is longer than the data "type" specification in the COLEXPR parameter Truncates shredded JSON data that is longer than the RETURNTYPE data size specification. Optionally, you can have TD_JSONSHRED fail with an error if the shredded data exceeds the type specification. The error indicates the problematic column.