This documentation is for a prior release of Kinetica. For the latest documentation, click
here.
Machine Learning (ML)
Kinetica provides support for Machine Learning (ML)
container registry & model creation and management in SQL. A Docker registry
serves as a container for ML models, while an ML model represents a function
from which an inference can be computed.
Note
For statistical analysis functions that don't require a model, see
ML Functions.
Container registry features accessible via SQL include:
The response to SHOW CONTAINER REGISTRY is a single-column result
set with the DDL statement as the value in the DDL column.
Parameters
Description
<registry name>
Name of the existing reference to the container registry for which the DDL will be output.
Use * instead to output the DDL of all references to container registries.
BATCH - inference tests are run against a batch of data in an existing table all at once
CONTINUOUS - inference tests are run automatically against records being streamed into an
input table; inference results are inserted into an output table, which will be updated upon
each subsequent inference
Note
Continuous deployment mode is only available when using the EXECUTE FUNCTION
syntax, as it creates a destination table with the continuously updated results.
REPLICATIONS
The number of replicas to launch on Kubernetes
SOURCE_TABLE
Table or query to use as input to the ML model, specified with either of these two forms:
INPUT_TABLE(<table name>) - Use the given table or view as input; e.g.:
INPUT_TABLE(price_history)
INPUT_TABLE(<query>) - Use the given query as input; e.g.:
INPUT_TABLE(SELECT ts, item, price FROM price_history)
DESTINATION_TABLE
Only applicable when using EXECUTE FUNCTION syntax. Name of the table in which to store the
results of the inference, in [schema_name.]table_name format, using standard
name resolution rules and meeting
table naming criteria
The response to DESCRIBE MODEL is a four-column result set:
MODEL - name of the ML model
ENTITY_ID - internal unique ID for the ML model
INPUT_SCHEMA - list of columns types that valid input data is expected
to match
OUTPUT_SCHEMA - list of column types that will either be returned by
the model as a result set or used in creating a result table, depending on
how the model's evaluation is invoked
Parameters
Description
<model name>
Name of the existing model for which the configuration will be output. Use * instead
to output the configuration of all models.