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] Add Hive metadata entity serde and storage support #91

Closed
Tracked by #58
jerryshao opened this issue Jul 7, 2023 · 1 comment · Fixed by #208
Closed
Tracked by #58

[Subtask] Add Hive metadata entity serde and storage support #91

jerryshao opened this issue Jul 7, 2023 · 1 comment · Fixed by #208
Assignees
Labels
subtask Subtasks of umbrella issue

Comments

@jerryshao
Copy link
Contributor

jerryshao commented Jul 7, 2023

Describe the subtask

We should support serializing and deserializing HiveCatalog-specific entities, like HiveSchema, HiveTable and HiveColumn later on. So that we could store the additional entity information to our own storage.

Parent issue

#58

@jerryshao jerryshao added the subtask Subtasks of umbrella issue label Jul 7, 2023
@jerryshao jerryshao added this to the Graviton v0.2.0 milestone Jul 25, 2023
@jerryshao
Copy link
Contributor Author

@mchades I assigned this to you, please define the hive entity value to ser-deser and store.

jerryshao pushed a commit that referenced this issue Aug 14, 2023
### What changes were proposed in this pull request?

1. Add `CommonSchema` class and  `Schema` proto for serde
2. serde and store `HiveSchema` as `CommonSchema`
3. hive schema operations support Graviton store

### Why are the changes needed?

we could store the additional entity information to our own storage.

Fix: #91 

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

Add some check for Graviton store

### How was this patch tested?
UTs added
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.

2 participants