Implement Remaining Catalog operations for REST catalog
Feature Request / Improvement
DropTable and RenameTable both are not yet implemented for REST catalog and should get implemented.
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?
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.
@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?
Go ahead and put the PR up and we'll discuss and iterate! Thanks!