Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-3607

Set mapreduce.task.classpath.user.precedence to true by default

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 0.10.0
    • Fix Version/s: None
    • Component/s: Configuration
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                kevinwilfong Kevin Wilfong
                Reporter:
                kevinwilfong Kevin Wilfong
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: