rdblue commented on pull request #4017: URL: https://github.com/apache/iceberg/pull/4017#issuecomment-1030917342
I understand the proposal, but I still think that the current behavior is correct. The Hive environment comes from Hive. If Hive is enabled in that environment, then it means that you expect to have the Iceberg classes available everywhere. There should be no need for redundant settings at the table level (which overrides the environment). And in addition, if the Hive environment changes, then so should this behavior. Adding this at the table level leaks Hive environment from some point in time into a table forever. It would be good to hear more about how you encountered this to recommend a way to fix it. I suspect that your Hive environment was out of sync across the clusters? Did that reflect the state of the clusters as well -- meaning were you also inconsistently including Iceberg in the classpath? -- 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 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
