Skip to content
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

[#86] refactor(catalog): Change the Namespace semantics to Schema in catalog definition #87

Merged
merged 3 commits into from
Jul 7, 2023

Conversation

jerryshao
Copy link
Collaborator

What changes were proposed in this pull request?

This PR proposes to change SupportNamespaces to SupportSchemas, and introduces Schema (aka. database) terminology to Graviton's catalog system.

Also, this PR refactors the current HiveCatalog a bit to suit the new interface.

Why are the changes needed?

As mentioned in #86 , the current Namespace in Graviton has two meanings, which may be confusing for developers.

  1. Namespace in NameIdentifer defines the name prefix of an identifier, for example, a catalog "metalake.catalog" has Namespace "metalake".
  2. namespace in the catalog's SupportNamepaces mainly stands for database, or the entity repository under catalog, which differs from the thing mentioned in No.1.

So here we propose a change to the current definitions to make them more distinguishable.

Fix: #86

Does this PR introduce any user-facing change?

Introduce new SupportSchemas interfaces and remove the SupportNamespaces.

How was this patch tested?

Existing UTs.

@jerryshao jerryshao requested a review from xunliu July 6, 2023 07:49
@jerryshao jerryshao self-assigned this Jul 6, 2023
@jerryshao
Copy link
Collaborator Author

@xunliu please take time to review this PR, I changed the semantics a bit.

Copy link
Collaborator

@xunliu xunliu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jerryshao jerryshao merged commit 9a2f7c2 into datastrato:main Jul 7, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Improvement] Change SupportNamespaces to a different terminology to avoid naming conflicts
2 participants