wangyum opened a new pull request #24388: [SPARK-27481][BUILD] Upgrade commons-logging to 1.1.3 for hadoop-3.2 URL: https://github.com/apache/spark/pull/24388 ## What changes were proposed in this pull request? hadoop-2.7 gets `commons-logging` version from `hive-metastore`: ``` [INFO] +- org.spark-project.hive:hive-metastore:jar:1.2.1.spark2:compile [INFO] | +- com.jolbox:bonecp:jar:0.8.0.RELEASE:compile [INFO] | +- commons-cli:commons-cli:jar:1.2:compile [INFO] | +- commons-logging:commons-logging:jar:1.1.3:compile ``` But Hive removes `commons-logging` since [HIVE-12237(Hive 2.0.0)](https://issues.apache.org/jira/browse/HIVE-12237), so hadoop-3.2 gets `commons-logging` from `commons-httpclient`: ``` [INFO] +- commons-httpclient:commons-httpclient:jar:3.1:compile [INFO] | \- commons-logging:commons-logging:jar:1.0.4:compile ``` Thus. we may hint `LogConfigurationException`: ``` bin/spark-sql --conf spark.sql.hive.metastore.version=1.2.2 --conf spark.sql.hive.metastore.jars=file:///apache/hive-1.2.2-bin/lib/* ... Caused by: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:385) ... 43 more ``` This pr upgrade `commons-logging` to 1.1.3 for hadoop-3.2 to fix this issue. ## How was this patch tested? manual tests
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
