Hive
  1. Hive
  2. HIVE-5725

Separate out ql code from exec jar

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Build Infrastructure
    • Labels:
      None

      Description

      We should publish our code independently from our dependencies. Since the exec jar has to include the runtime dependencies, I'd propose that we make two jars, a ql jar and and exec jar.

        Issue Links

          Activity

          Owen O'Malley created issue -
          Hide
          Brock Noland added a comment -

          I'd propose we do away with the exec uber jar and utilize the libjars functionality to push the dependencies into the class path.

          Show
          Brock Noland added a comment - I'd propose we do away with the exec uber jar and utilize the libjars functionality to push the dependencies into the class path.
          Jarek Jarcec Cecho made changes -
          Field Original Value New Value
          Link This issue relates to HIVE-5733 [ HIVE-5733 ]
          Hide
          Shevek added a comment -

          +1 - we are losing days of development work working around this packaging misfeature.

          Show
          Shevek added a comment - +1 - we are losing days of development work working around this packaging misfeature.
          Hide
          murali namburi added a comment -

          +1 this is causing issue to use hive-exec jar, it always having conflicts with jackson jars

          Show
          murali namburi added a comment - +1 this is causing issue to use hive-exec jar, it always having conflicts with jackson jars
          Brock Noland made changes -
          Link This issue relates to HIVE-860 [ HIVE-860 ]
          Hide
          Brock Noland added a comment -

          I think the purpose originally for the fat jar was so that we only had to ship a single jar. With HIVE-860 shipping multiple jars will be quite easy.

          Show
          Brock Noland added a comment - I think the purpose originally for the fat jar was so that we only had to ship a single jar. With HIVE-860 shipping multiple jars will be quite easy.
          Hide
          E. Sammer added a comment -

          Another +1. We just hit this and it's causing us serious pain. I was surprised that the shaded classes weren't relocated. As it stands today, using the JDBC driver seems to suck in hive-exec at the end of the rainbow, meaning any application that uses Guava (or Jackson, or...) gets burned unless they happen to be using the same version as Hive.

          Show
          E. Sammer added a comment - Another +1. We just hit this and it's causing us serious pain. I was surprised that the shaded classes weren't relocated. As it stands today, using the JDBC driver seems to suck in hive-exec at the end of the rainbow, meaning any application that uses Guava (or Jackson, or...) gets burned unless they happen to be using the same version as Hive.
          Hide
          Michael Prim added a comment -

          +1, Took us this week some time to debug and find out that there is another Guava version spooking around in the classpath of hive which breaks our own code

          Show
          Michael Prim added a comment - +1, Took us this week some time to debug and find out that there is another Guava version spooking around in the classpath of hive which breaks our own code

            People

            • Assignee:
              Owen O'Malley
              Reporter:
              Owen O'Malley
            • Votes:
              3 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:

                Development