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 Catalog APIs in Gravitino Python client #2252

Closed
Tracked by #2113
xunliu opened this issue Feb 19, 2024 · 2 comments
Closed
Tracked by #2113

[Subtask] Add Catalog APIs in Gravitino Python client #2252

xunliu opened this issue Feb 19, 2024 · 2 comments
Assignees
Labels
subtask Subtasks of umbrella issue

Comments

@xunliu
Copy link
Member

xunliu commented Feb 19, 2024

Describe the subtask

Add these Python function interfaces into Gravitino Python client, reference to the document for the API descriptions.

We can reference the Gravitino JAVA client implementation, GravitinoMetaLake.java

Parent issue

#2113

@xunliu xunliu added the subtask Subtasks of umbrella issue label Feb 19, 2024
@xunliu xunliu added this to the Gravitino 0.5.0 milestone Feb 19, 2024
@shaofengshi
Copy link
Contributor

Brandon, would you like to take this? @Lanznx

@Lanznx
Copy link
Contributor

Lanznx commented Mar 9, 2024

YES, I'm willing to implement this

@xunliu xunliu self-assigned this Apr 7, 2024
xunliu added a commit that referenced this issue Apr 13, 2024
…n client (#2898)

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

Support Fileset Catalog in Python client, support below functions:

1. list_filesets()
2. load_fileset()
3. create_fileset()
4. alter_fileset()
5. drop_fileset()

### Why are the changes needed?

Fix: #2470 #2252 #2253

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

N/A

### How was this patch tested?

CI Passed
@xunliu xunliu closed this as completed Apr 13, 2024
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

No branches or pull requests

3 participants