XPSColumnSpec
import type { XPSColumnSpec } from "https://googleapis.deno.dev/v1/language:v2.ts";interface XPSColumnSpec {
columnId?: number;
dataStats?: XPSDataStats;
dataType?: XPSDataType;
displayName?: string;
forecastingMetadata?: XPSColumnSpecForecastingMetadata;
topCorrelatedColumns?: XPSColumnSpecCorrelatedColumn[];
}§Properties
§
columnId?: number
[src]The unique id of the column. When Preprocess, the Tables BE will popuate the order id of the column, which reflects the order of the column inside the table, i.e. 0 means the first column in the table, N-1 means the last column. AutoML BE will persist this order id in Spanner and set the order id here when calling RefreshTablesStats and Train. Note: it's different than the column_spec_id that is generated in AutoML BE.
§
dataStats?: XPSDataStats
[src]The data stats of the column. It's outputed in RefreshTablesStats and a required input for Train.
§
dataType?: XPSDataType
[src]The data type of the column. It's outputed in Preprocess rpc and a required input for RefreshTablesStats and Train.
§
displayName?: string
[src]The display name of the column. It's outputed in Preprocess and a required input for RefreshTablesStats and Train.
§
forecastingMetadata?: XPSColumnSpecForecastingMetadata
[src]