jackye1995 commented on pull request #3367: URL: https://github.com/apache/iceberg/pull/3367#issuecomment-952399204
So far `Catalog` has been a pluggable concept for cloud service integrations. It does not affect any Iceberg specific features, those are always controlled by the compute engine. Now we are saying that the `NessieCatalog` itself is more or less a compute engine that has its own list of unique features that other catalog cannot use. This is a big shift to the Iceberg catalog concept, and people can no longer easily switch across different implementations because of these catalog-specific procedures. it almost feel to me that Nessie should just implement another `NessieSparkCatalog` for Nessie users, and you can freely add all the extensions you'd like to have. I am also curious what approach you are taking for Delta Lake. They also have `io.delta.sql.DeltaSparkSessionExtension`, are you also adding a similar hook on their side? -- 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]
