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

[Subtask] Refactor the schema system #44

Closed
Tracked by #43
jerryshao opened this issue Jun 6, 2023 · 0 comments · Fixed by #45
Closed
Tracked by #43

[Subtask] Refactor the schema system #44

jerryshao opened this issue Jun 6, 2023 · 0 comments · Fixed by #45
Assignees
Labels
subtask Subtasks of umbrella issue

Comments

@jerryshao
Copy link
Collaborator

Describe the subtask

This issue tracks to refactor the schema system:

  1. Simplify the current "tenant/lakehouse/zone/table" logical structure.
  2. reorganize the project structure.
  3. Abstract the common entities and make them inheritable.

Parent issue

#43

@jerryshao jerryshao added the subtask Subtasks of umbrella issue label Jun 6, 2023
@jerryshao jerryshao self-assigned this Jun 6, 2023
jerryshao added a commit that referenced this issue Jun 14, 2023
…#45)

### What changes were proposed in this pull request?

This PR changes include:

1. refactors the whole metadata system, which simplifies the current
tenant/lakehouse/zone/table schema structure to
lakehouse/catalog/<meta-structure> (refer to what metacat did).
2. Add catalog interfaces and define a series of catalog behaviors. the
specific catalog implementation could inherit these interfaces to
achieve its own one (refer to what Spark connector/catalog did).
3. rearchitect the code structure.

### Why are the changes needed?

As #43 described, the current schema system is a bit difficult to manage
(to pursue virtual semantics), we needs to simplify the current design.

Fix: #44

### Does this PR introduce _any_ user-facing change?

We're still in the early stage of the project, the change is unavoidable
and acceptable.

### How was this patch tested?

UTs to cover the codes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
subtask Subtasks of umbrella issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant