View the Partition Structure | Native Object Store ( NOS ) | Teradata Vantage - 17.05 - Viewing the Key Structure - Teradata Database

Teradata Vantageā„¢ - Native Object Store Getting Started Guide

prodname
Advanced SQL Engine
Teradata Database
vrm_release
17.05
created_date
January 2021
category
Programming Reference
featnum
B035-1214-175K

JSON data stored on external object store has two parts: a key (also called a path) and a payload.

Key
A key prefix that identifies a set of objects to be enumerated. Given the key structure of the td-usgs bucket, which contains United States Geological Survey river flow data data / siteno / year / month / day, an example key is /S3/td-usgs.s3.amazonaws.com/JSONDATA/09380000/2018/07.
Payload
Contains the values in the object; for example, datetime, Flow, Velocity, Precipitation, Temp, GageHeight.

The examples and results show a sample river flow data set. To use your own data, replace the table and column names, and authorization object.

  1. To run NOS-related commands, log on to the database as a user with the required privileges.
  2. Display some of the keys in a given location:
    SELECT TOP 2 LOCATION FROM READ_NOS_FM (
    USING
    RETURNTYPE ('NOSREAD_KEYS')
    LOCATION('YOUR-STORAGE-ACCOUNT')
    ) AS D;

    See Variable Substitutions for Examples for the credentials and location values for the sample river flow data set.

    Your result will be similar to this, reflecting your external object store location:

    Location
    ---------------------------------------------------------------------
    /S3/td-usgs.s3.amazonaws.com/JSONDATA/09380000/2018/06/28.json
    /S3/td-usgs.s3.amazonaws.com/JSONDATA/09380000/2018/06/29.json