dengc367 commented on PR #14310:
URL: https://github.com/apache/gravitino/pull/14310#issuecomment-6502655881
Summary of where this design now sits, and how it maps to the reference,
because the conclusion changed
since the first revision of this PR.
**The correspondence.** Semantic Models ↔ metric views (already in `main`),
Domains ↔ Domains (landing on
`branch-domain-dev`), Glossary Terms ↔ Pages (PR #14239), and Certification
↔ nothing in Gravitino today.
**An Ontology is not a Genie Ontology.** The Genie Ontology is not a stored
object: it is a context layer
Genie One computes at query time from the four modeled components plus
context it infers from assets and
usage. There is no Gravitino object that corresponds to it, so a stored
`Ontology` would be a component
invented from the Ossie specification's shape rather than from a stated user
need.
**So this design is now an export, not an entity.** `GET
.../semantic-models/{model}/ossie-ontology`
renders a validated Ossie document from metadata Gravitino already has.
Nothing is stored, so the design no
longer needs a scope, a status vocabulary, a version snapshot table, a
privilege family or a lifecycle. The
previous revision's hardest questions — concept identity across renames,
relationship identity, version
migration, mapping placement — were all caused by storage and disappear by
construction. Alternatives
Considered records the stored-entity design and why it was dropped.
What survives from the earlier revision is the part that was never about
storage: the Ossie document model,
the closed-root validation, the required `verbalizes` and the rejection of
dangling concept names. That
work is PR #14371, reduced from 23 files to 11.
@mchades @jerryshao since you looked at the first revision: the document is
shorter now (263 lines, down
from 495) and the read that matters is the shape change — a read-only export
rather than a new metadata
object. #14367 and #14369 track the two remaining slices; the storage and
CRUD pull requests are closed.
--
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]
