Views and Path Filtering | Native Object Store ( NOS ) | Teradata Vantage - Using Views and Path Filtering - Analytics Database - Teradata Vantage

Teradata Vantage™ - Native Object Store Getting Started Guide - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2024-04-05
dita:mapPath
tsq1628112323282.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
jjn1567647976698
Product Category
Teradata Vantage

There are specific benefits to creating foreign table views, in addition to the usual reasons of security and hiding SQL complexity. These benefits include:

  • Makes it easier to query object store data with inconsistent uppercase and lowercase field names. CSV field names are case sensitive, but Teradata SQL is case insensitive.
  • You can hide the $path references in a foreign table and make path names look like standard column names.

Follow these recommendations when creating a view on a foreign table:

  • Include both path names and payload attributes as columns in the view.
  • CAST all values in the view to an appropriate data type.
  • It is often the case that the path segment name (such as site_no in data / site_no / year / month / day) is also represented by an attribute in your data. When this is true, Teradata recommends you equate them in the WHERE expression in the view and only specify one of them in the column list.