shubham-tomar commented on issue #291: URL: https://github.com/apache/iceberg-go/issues/291#issuecomment-2653078482
Hi @zeroshade, @kevinjqliu, I want to use Nessie as a catalog for Iceberg in my data pipeline, which is entirely written in Go. Given the discussion around my PR, I want to clarify the best approach moving forward. Would it make sense to fork iceberg-go and create a dedicated catalog/nessie package that: - Implements Nessie-specific API paths and structures while keeping compatibility with Iceberg. - Use the core functionalities of iceberg-go, ensuring minimal duplication and consistency with the Iceberg ecosystem. This way, I wouldn’t modify catalog/rest directly but instead build a separate Nessie catalog implementation within my fork. Does this sound like the right approach, or do you have alternative recommendations? Essentially i wanted to use Nessie for branching logic, and iceberg-go for data CRUD operations Thanks for your guidance! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
