[
https://issues.apache.org/jira/browse/OOZIE-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004136#comment-16004136
]
Peter Cseh commented on OOZIE-2780:
-----------------------------------
so I've run a depenency:tree -Dhadoop.version=2.7.0
When the hadoop component is referenced in our poms, the versions are correct.
Where the dependencies are only transitive, they'll stay at 2.6.0, mostly via
hive-something:
{noformat}
+- org.apache.hive.shims:hive-shims-0.23:jar:1.2.0:runtime
[INFO] | | | | \-
org.apache.hadoop:hadoop-yarn-server-resourcemanager:jar:2.6.0:runtime
[INFO] | | | | +- org.apache.hadoop:hadoop-annotations:jar:2.6.0:runtime
,,,,
[INFO] | | | | +- org.apache.hadoop:hadoop-yarn-common:jar:2.6.0:runtime
[INFO] | | | | +- org.apache.hadoop:hadoop-yarn-api:jar:2.6.0:runtime
{noformat}
I don't think we can do too many things about this.
> Upgrade minimum Hadoop version to 2.6.0
> ---------------------------------------
>
> Key: OOZIE-2780
> URL: https://issues.apache.org/jira/browse/OOZIE-2780
> Project: Oozie
> Issue Type: Improvement
> Components: core
> Affects Versions: 4.3.0
> Reporter: Artem Ervits
> Assignee: Artem Ervits
> Priority: Minor
> Labels: newbie
> Attachments: OOZIE-2780-0.patch, OOZIE-2780-1.patch,
> OOZIE-2780-2.patch
>
>
> I'd like to contribute an fs action enhancement to modify extended attributes
> to core but methods to change extended attributes is not available in
> hadoop-common < 2.6.0. Currently hadoop-common is at 2.4. I am contributing a
> patch to bump to 2.6 but so far I haven't been able to generate a clean test
> as tests in core module fail randomly. On the first run, I had a failure on
> {code} Failed tests:
> testCheckAfterActionDelete(org.apache.oozie.service.TestHAPartitionDependencyManagerService):
> Expected: <null> but was: [0000000-170123095541655-oozie-aerv-C@1]{code}
> and on second run
> {code}Failed tests: testWaitFor(org.apache.oozie.test.TestXTestCase):
> expected:<1000.0> but was:<2036.0>{code}
> I can't tell whether it is due to my patch?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)