Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-3185

Upgrade org.apache.derby to 10.11.1.1

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.1.0
    • Component/s: core
    • Labels:
      None

      Description

      Hi, by analyzing oozie-master\core\pom.xml, I found that there are two versions of org.apache.derby:derby. Their introduced paths are:

      1. org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.derby:derby:10.10.1.1::compile

      2. org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.hive:hive-exec:1.2.0:core:compile->org.apache.hive:hive-metastore:1.2.0::compile->org.apache.derby:derby:10.11.1.1::compile

      Of them, org.apache.derby:derby:10.10.1.1 is the transitively introduced by org.apache.hive:hive-exec and org.apache.derby:derby:10.11.1.1 is the direct dependency. By further analyzing the source code, we found they have too many different features.

      Also, I found that you have already gave derby a exclusion tag when transitively introducing derby by hive-beeline to avoid dependency conflict.

      So it would be nice to keep the consistency of library version for the project long-term health, maybe update org.apache.derby:derby from 10.10.1.1 to 10.11.1.1, or exclude derby from hive-exec is a good choice. Hope this can help you. Thanks.

        Attachments

        1. oozie.txt
          429 kB
          PandaMonkey
        2. 0001-Fix1.patch
          0.7 kB
          PandaMonkey

          Issue Links

            Activity

              People

              • Assignee:
                PandaMonkey PandaMonkey
                Reporter:
                PandaMonkey PandaMonkey
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: