You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Eugene Shevchuk (JIRA)" <ji...@apache.org> on 2013/08/13 13:30:49 UTC

[jira] [Reopened] (OOZIE-1494) 100% system tests pass for Oozie on Windows (HDP 1.3)

     [ https://issues.apache.org/jira/browse/OOZIE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eugene Shevchuk reopened OOZIE-1494:
------------------------------------

    
> 100% system tests pass for Oozie on Windows (HDP 1.3)
> -----------------------------------------------------
>
>                 Key: OOZIE-1494
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1494
>             Project: Oozie
>          Issue Type: Task
>            Reporter: Eugene Shevchuk
>         Attachments: certification.patch, oozie-sources.patch
>
>
> To achieve successful pass of all Oozie system tests on windows with HDP 1.3 the following changes were made:
>  Product code changes:
>   - mapper and reducer parameters in oozie demo and streaming example were carried out as variables whose values are placed in respective job.properties
>   - modified launch command in oozie.cmd
>   - security in authorization service has been enabled by default
>  System tests modifications:
>   tests/oozie/oozie-regression/src/main/java/com/yahoo/oozie/test/XTestCase.java
>    Added public boolean stringsEqualByData(String, String) method which compares two string w/o '\n' and '\r' symbols
>   tests/oozie/oozie-regression/src/main/java/com/yahoo/oozie/test/XTestVerifyJob.java
>    Expressions in if statements was replaced from 'str1.compareTo(str2) == 0' to 'stringsEqualByData(str1, str2)'
>   beaver/component/oozie.py
>    Added parameter '"-Doozie.auth.token.cache=false"' to oozie_cmd job launch command, parameters for oozie were double-quoted, increased timeout for successful test run on slow machines
>   tests/oozie/oozie-regression/lib/original-yoozietest-qa-1.0.0-SNAPSHOT.jar
>   tests/oozie/oozie-regression/lib/yoozietest-qa-1.0.0-SNAPSHOT.jar
>    Replaced by more fresh versions
>   tests/oozie/proxy/test_proxySettingsCli.py  
>   tests/oozie/oozie-regression/src/main/java/com/yahoo/oozie/testrel1x/TestWfKillSubwf2.java
>   tests/oozie/oozie-regression/src/main/java/com/yahoo/oozie/testrel21/TestCoordRerun6.java
>   tests/oozie/oozie-regression/src/main/java/com/yahoo/oozie/testrel1x/TestWfKill.java
>   tests/oozie/oozie-regression/src/main/java/com/yahoo/oozie/testrel1x/TestWfKillSubwf1.java
>   tests/oozie/oozie-regression/src/main/java/com/yahoo/oozie/testrel312/TestCoordDsErr.java
>    Increased timeout for successful test run on slow machines
>   tests/oozie/statechanges/test_ooziestatechanges_wf.py
>    Increased timeout for successful test run on slow machines, waiting for workflow status changes was implemented in another way
>   tests/oozie/End2End/test_e2eoozie.py
>    distcp test for Windows was enabled for running
> Attached patches with product code changes and system tests updates.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira