[ https://issues.apache.org/jira/browse/HIVE-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726925#comment-13726925 ]
Konstantin Boudnik commented on HIVE-3607: ------------------------------------------ Are there any plans to commit this and HIVE-3606 in the bugfix release for Hive 0.11 (if any?) > Set mapreduce.task.classpath.user.precedence to true by default > --------------------------------------------------------------- > > Key: HIVE-3607 > URL: https://issues.apache.org/jira/browse/HIVE-3607 > Project: Hive > Issue Type: Improvement > Components: Configuration > Affects Versions: 0.10.0 > Reporter: Kevin Wilfong > Assignee: Kevin Wilfong > > When queries are actually run in a Hadoop cluster, Hive's jars are appended > to Hadoop's classpath. However, when we test/run jobs locally Hive's > classpath comes first. This leads to issues like the one brought up here > after the patch was committed HIVE-3581 where a change depended on a jar Hive > includes which conflicted with one provided by Hadoop which is an older > version in 0.20 > It's possible that more of the jars we include are getting preceded by older > jars in Hadoop, and we haven't noticed yet. > If we add Hive jars to the beginning of Hadoop's classpath we will be in > control in such situations where the jars are backwards compatible. We will > be able to update the jars in Hive and these will be used at run time, > instead of just compile time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira