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

Implement Remaining Catalog operations for REST catalog #63

Open
zeroshade opened this issue Feb 14, 2024 · 4 comments
Open

Implement Remaining Catalog operations for REST catalog #63

zeroshade opened this issue Feb 14, 2024 · 4 comments

Comments

@zeroshade
Copy link
Member

Feature Request / Improvement

DropTable and RenameTable both are not yet implemented for REST catalog and should get implemented.

@rtadepalli
Copy link

Trying to implement RenameTable using the OpenAPI spec listed here: https://github.com/apache/iceberg/blob/main/open-api/rest-catalog-open-api.yaml

Is that correct? If so, I don't see createTable implemented yet. I think that is required to test RenameTable. Should that be implemented first?

@zeroshade
Copy link
Member Author

Is that correct? If so, I don't see createTable implemented yet. I think that is required to test RenameTable. Should that be implemented first?

Most likely, yes.

@jhump
Copy link
Contributor

jhump commented Oct 11, 2024

@zeroshade, I've got a fork where I've implemented DropTable and added CreateTable and UpdateTable, which have the most complicated API. Did you already have ideas on what the API might look like? Or should I just put up a PR with what I have and we can discuss/iterate on the API?

@zeroshade
Copy link
Member Author

Go ahead and put the PR up and we'll discuss and iterate! Thanks!

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

No branches or pull requests

3 participants