yabola commented on PR #1478: URL: https://github.com/apache/iceberg/pull/1478#issuecomment-3199183134
@marton-bod @rdblue Hi, Spark connects to Hive3 through a separate classloader to load the Hive3 related jars ( `spark.sql.hive.metastore.jars` for Hive3 jars, as referenced in `org.apache.spark.sql.hive.HiveUtils#newClientForMetadata`). Under this scenario, the Spark JVM's default classloader still use Hive2 classes, and Iceberg side will still retrieves the Hive2 client (although the interface is compatible, but the new features of hive3 cannot be used). Can I add an future to use a separate classloader when creating a new hive client ,witch similar to Spark's approach if we use hive3 ? Do you have any suggestions? -- 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]
