jerryshao commented on code in PR #14038:
URL: https://github.com/apache/gravitino/pull/14038#discussion_r4335816293


##########
design-docs/gravitino-schema-metrics-discovery-design.md:
##########
@@ -0,0 +1,391 @@
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one
+  or more contributor license agreements.  See the NOTICE file
+  distributed with this work for additional information
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+-->
+
+# Design of Schema-level Semantic Model Metrics Discovery in Gravitino
+
+## Background
+
+Metrics in Gravitino are defined within Semantic Models. To browse or select 
metrics across a
+schema, clients currently list the Semantic Models, load each model, and 
extract its metrics.
+
+This requires a separate request to load each model and returns the full 
definitions, including
+datasets and relationships that metric discovery does not need. Clients must 
also implement the
+collection logic themselves. The number of requests and volume of metadata 
transferred increase
+as more models are added or their definitions grow.
+
+## Goals
+
+1. **Discovery.** Provide schema-level listing of metric identifiers and 
complete definitions through
+   REST, Java, Python, and MCP, without requiring clients to load each 
Semantic Model separately.

Review Comment:
   Do yo still need to know the semantic mode name to list the metrics?



-- 
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