[
https://issues.apache.org/jira/browse/OOZIE-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008590#comment-16008590
]
Artem Ervits commented on OOZIE-2780:
-------------------------------------
[~pbacsko] for the one test that definitely fails with 2.6, I see the following
https://github.com/apache/oozie/blob/master/core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java#L2485-L2491,
if configuration is not set, property
{code}
yarn.timeline-service.enabled
{code}
as per
https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/TimelineServer.html
defaults to false, so doesn't the test
{code}
assertEquals("true",
launcherConf.get(JavaActionExecutor.HADOOP_YARN_TIMELINE_SERVICE_ENABLED));
{code}
need to expect false, rather than true?
then a few more tests for the property check the expected property in multiple
ways
{code}
assertEquals("true",
launcherConf.get(JavaActionExecutor.HADOOP_YARN_TIMELINE_SERVICE_ENABLED));
{code}
and
{code}
assertTrue(launcherConf.getBoolean(JavaActionExecutor.HADOOP_YARN_TIMELINE_SERVICE_ENABLED,
false));
{code}
[~rkanter] please advise? Again, this test passes if I exclude commons-io from
hadoop project or increase the commons-io version from 2.1 to 2.4 in main Oozie
pom.
> 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
> Fix For: 5.0.0
>
> 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)
