Skip to main content
Version: 0.8.0-incubating

Model catalog

Introduction

A Model catalog is a metadata catalog that provides the unified interface to manage the metadata of machine learning models in a centralized way. It follows the typical Gravitino 3-level namespace (catalog, schema, and model) to manage the ML models metadata. In addition, it supports managing the versions for each model.

The advantages of using model catalog are:

  • Centralized management of ML models with user defined namespaces. Users can better discover and govern the models from sematic level, rather than managing the model files directly.
  • Version management for each model. Users can easily track the model versions and manage the model lifecycle.

The key concept of model management is to manage the path (URI) of the model. Instead of managing the model storage path physically and separately, model metadata defines the mapping relation between the model name and the storage path. In the meantime, with the support of extensible properties of model metadata, users can define the model metadata with more detailed information rather than just the storage path.

  • Model: A model is a metadata object defined in the model catalog, to manage a ML model. Each model can have many Model Versions, and each version can have its own properties. Models can be retrieved by the name.
  • ModelVersion: The model version is a metadata defined in the model catalog, to manage each version of the ML model. Each version has a unique version number, and can have its own properties and storage path. ModelVersion can be retrieved by the model name and version number. Also, each version can have a list of aliases, which can also be used to retrieve.

Catalog

Catalog properties

A Model catalog doesn't have specific properties. It uses the common catalog properties.

Catalog operations

Refer to Catalog operations for more details.

Schema

Schema capabilities

Schema is the second level of the model catalog namespace, the model catalog supports creating, updating, deleting, and listing schemas.

Schema properties

Schema in the model catalog doesn't have predefined properties. Users can define the properties for each schema.

Schema operations

Refer to Schema operation for more details.

Model

Model capabilities

The Model catalog supports registering, listing and deleting models and model versions.

Model properties

Model doesn't have predefined properties. Users can define the properties for each model and model version.

Model operations

Refer to Model operation for more details.

ModelVersion

ModelVersion capabilities

The Model catalog supports linking, listing and deleting model versions.

ModelVersion properties

ModelVersion doesn't have predefined properties. Users can define the properties for each version.

ModelVersion operations

Refer to ModelVersion operation for more details.