Using Partition by Key (Micromodeling) - Analytics Database

Database Analytic Functions

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2024-04-06
dita:mapPath
gjn1627595495337.ditamap
dita:ditavalPath
ayr1485454803741.ditaval
dita:id
jmh1512506877710
Product Category
Teradata Vantageā„¢
When it is used as partition-by-key function to train each partition as a single model, the function accepts the following inputs:
  • InputTable is required, containing an input dataset to be used for training GLM per segment model.
  • AttributeTable is optional, defining a subset of features to be used with respect to each partition.
  • ParameterTable is optional, defining a subset of parameters to be used with respect to each partition.

The ORDER BY clause can be optionally applied to the InputTable to guarantee the result in each run is deterministic. The situation of indeterministic result in a partition can occur if the BatchSize argument is less than the number of rows in the partition. Adding the ORDER BY clause ensures the result is deterministic regardless of the BatchSize settings. The ORDER BY clause can affect performance.