-
Notifications
You must be signed in to change notification settings - Fork 416
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#5744]feat(catalog-model): Add a basic catalog-model framework in Gravitino #5757
Conversation
...s/catalog-model/src/main/java/org/apache/gravitino/catalog/model/ModelCatalogCapability.java
Outdated
Show resolved
Hide resolved
catalogs/catalog-model/src/main/java/org/apache/gravitino/catalog/model/ModelCatalog.java
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
* catalog should be created. The short name: | ||
* | ||
* <p>1) should be the same as the {@link CatalogProvider} interface provided. 2) can be "null" if | ||
* the created catalog is a built-in catalog, like model catalog. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm very puzzle about the concept of built-in
catalog, can you explain it more clearly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And, so the provider of all built-in catalogs is null?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me add more comment to explain the concept introduced here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the user level, the "provider" value can be null, user doesn't need to provide the "provider" for those catalogs.
From the Gravitino kernel, it will treat the catalog "type" name as the "provider" name, and use this name to load in the catalog.
common/src/main/java/org/apache/gravitino/dto/requests/CatalogCreateRequest.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM.
… in Gravitino (apache#5757) ### What changes were proposed in this pull request? This PR adds the basic catalog-model framework in Gravitino. In the meantime, it also makes `provider` optional for built-in catalog. ### Why are the changes needed? Fix: apache#5744 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Tests will be added later on.
What changes were proposed in this pull request?
This PR adds the basic catalog-model framework in Gravitino. In the meantime, it also makes
provider
optional for built-in catalog.Why are the changes needed?
Fix: #5744
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Tests will be added later on.