mchades commented on code in PR #6052:
URL: https://github.com/apache/gravitino/pull/6052#discussion_r1903875022


##########
docs/model-catalog.md:
##########
@@ -0,0 +1,87 @@
+---
+title: "Model catalog"
+slug: /model-catalog
+date: 2024-12-26
+keyword: model catalog
+license: "This software is licensed under the Apache License version 2."
+---
+
+## 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

Review Comment:
   need include `metalake`?



##########
docs/overview.md:
##########
@@ -63,24 +63,28 @@ change the existing SQL dialects.
 In the meantime, other query engine support is on the roadmap, including
 [Apache Spark](https://spark.apache.org/), [Apache 
Flink](https://flink.apache.org/) and others.
 
-### AI asset management (WIP)
+### AI asset management
 
-The goal of Gravitino is to unify the data management in both data and AI 
assets. The support of AI
-assets like models, features, and others are under development.
+The goal of Gravitino is to unify the data management in both data and AI 
assets, including raw files, models, etc.
 
 ## Terminology
 
-### The model of Apache Gravitino
-
-![Gravitino Model](assets/metadata-model.png)
+### The metadata object of Apache Gravitino
 
 * **Metalake**: The top-level container for metadata. Typically, one group has 
one metalake
   to manage all the metadata in it. Each metalake exposes a three-level 
namespace(catalog.schema.
   table) to organize the data.
 * **Catalog**: A catalog is a collection of metadata from a specific metadata 
source.
   Each catalog has a related connector to connect to the specific metadata 
source.
-* **Schema**: A schema is equivalent to a database, Schemas only exist in the 
specific catalogs
-  that support relational metadata sources, such as Apache Hive, MySQL, 
PostgreSQL, and others.
+* **Schema**: Schema is the second level namespace to group a collection of 
metadata, schema can

Review Comment:
   third level namespace?



##########
docs/manage-model-metadata-using-gravitino.md:
##########
@@ -0,0 +1,637 @@
+---
+title: Manage model metadata using Gravitino
+slug: /manage-model-metadata-using-gravitino
+date: 2024-12-26
+keyword: Gravitino model metadata manage
+license: This software is licensed under the Apache License version 2.
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+This page introduces how to manage model metadata in Apache Gravitino. 
Gravitino model catalog
+is a kind of model registry, which provides the ability to manage machine 
learning models'
+versioned metadata. It follows the typical Gravitino 3-level namespace 
(catalog, schema, and
+model) and supports managing the versions for each model.

Review Comment:
   should the namespace includes `metalake`?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to