shubham-tomar opened a new issue, #291: URL: https://github.com/apache/iceberg-go/issues/291
### Feature Request / Improvement ### Description The current Catalog interface in iceberg-go is designed for the Iceberg REST catalog, but it does not fully align with Project Nessie’s API requirements. Nessie uses different API paths, request payloads, and reference (branch/tag) handling, which needs adjustments across all catalog operations. And it has different [API versions](https://app.swaggerhub.com/apis/projectnessie/nessie/0.102.4#/v1) too. For example, Namespace Creation CreateNamespace function in catalog/rest.go uses POST method while [nessie v1 api](https://app.swaggerhub.com/apis/projectnessie/nessie/0.102.4#/v1/createNamespace) uses PUT method API PATH is also different. I have seen similar issues with multiple functions I am willing to make changes to support Nessie apis, would appreciate some guidance on how to go about it? 1. Should we modify current catalog/rest - Use ref and other required params from context.Context for Nessie API. - Dynamically determine API paths based on whether Nessie or Iceberg REST Catalog is being used. 2. Create a new catalog/nessie to support and maintain nessie specific functionality separately -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
