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

Oozie can't be build against anything else but Hadoop 2.0.2-alpha

    Details

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

      Description

      Underlying hadoop version is hardcoded in multiple pom files across the project. The result is that Oozie can't be build against anything else but 2.0.0-alpha of Hadoop.

      1. BIGTOP-837.patch
        3 kB
        Konstantin Boudnik

        Issue Links

          Activity

          Hide
          rkanter Robert Kanter added a comment -

          I think we can fix this when we drop support for Hadoop 1.x and 0.23.x.
          Maybe for Oozie 5 we can finally do that and get rid of the whole hadooplibs thing which would simplify a lot of stuff

          Show
          rkanter Robert Kanter added a comment - I think we can fix this when we drop support for Hadoop 1.x and 0.23.x. Maybe for Oozie 5 we can finally do that and get rid of the whole hadooplibs thing which would simplify a lot of stuff
          Hide
          cos Konstantin Boudnik added a comment -

          It seems this won't ever get fixed. Or there's a chance still?

          Show
          cos Konstantin Boudnik added a comment - It seems this won't ever get fixed. Or there's a chance still?
          Hide
          cos Konstantin Boudnik added a comment -

          Sorry, I guess my brain was pollutted by Hive ;(

          What I was trying to say, is why the underlaying hadoop version needs to be a part of Oozie artifact's version? Would it better if Oozie is better isolated from Hadoop's API or whatever is the reason for the tight dependencies like this?

          Show
          cos Konstantin Boudnik added a comment - Sorry, I guess my brain was pollutted by Hive ;( What I was trying to say, is why the underlaying hadoop version needs to be a part of Oozie artifact's version? Would it better if Oozie is better isolated from Hadoop's API or whatever is the reason for the tight dependencies like this?
          Hide
          tucu00 Alejandro Abdelnur added a comment -

          ????

          Show
          tucu00 Alejandro Abdelnur added a comment - ????
          Hide
          cos Konstantin Boudnik added a comment -

          Even better solution would be, of course, a way of separating Oozie from Hadoop source code. A client application has no business of lurking into source code of a platform just to build itself.

          Show
          cos Konstantin Boudnik added a comment - Even better solution would be, of course, a way of separating Oozie from Hadoop source code. A client application has no business of lurking into source code of a platform just to build itself.
          Hide
          cos Konstantin Boudnik added a comment -

          Yeah, I see your point... I guess a better way needs to be devised. May be an autogeneration of the pom for the maven publishing during the build or something?

          Show
          cos Konstantin Boudnik added a comment - Yeah, I see your point... I guess a better way needs to be devised. May be an autogeneration of the pom for the maven publishing during the build or something?
          Hide
          tucu00 Alejandro Abdelnur added a comment -

          Cos, parameterizing versions in the dependencies is OK, however, parameterizing versions in the POM (parent or itself) it is not possible as it makes the POMs unusable from a Maven repo as the version must be resolved before pulling the parent (which in your patch is the one that defines the version). We'll have to work out a diff approach.

          Show
          tucu00 Alejandro Abdelnur added a comment - Cos, parameterizing versions in the dependencies is OK, however, parameterizing versions in the POM (parent or itself) it is not possible as it makes the POMs unusable from a Maven repo as the version must be resolved before pulling the parent (which in your patch is the one that defines the version). We'll have to work out a diff approach.
          Hide
          cos Konstantin Boudnik added a comment -

          That seems to do the trick, actually.

          Show
          cos Konstantin Boudnik added a comment - That seems to do the trick, actually.
          Hide
          cos Konstantin Boudnik added a comment -

          Build needs to be parametrized.

          Show
          cos Konstantin Boudnik added a comment - Build needs to be parametrized.

            People

            • Assignee:
              Unassigned
              Reporter:
              cos Konstantin Boudnik
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:

                Development