[
https://issues.apache.org/jira/browse/OOZIE-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469626#comment-13469626
]
Hadoop QA commented on OOZIE-822:
---------------------------------
Testing JIRA OOZIE-822
Cleaning local svn workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - the patch failed the following testcases:
. Tests run: 915
. Tests failures: 0
. Tests errors: 0
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}Overall result: Please check the reported -1(s){color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/132/
> Document that the Oozie Hive action creates a "hive-site.xml" file in the
> task's working directory
> --------------------------------------------------------------------------------------------------
>
> Key: OOZIE-822
> URL: https://issues.apache.org/jira/browse/OOZIE-822
> Project: Oozie
> Issue Type: Improvement
> Components: action
> Affects Versions: 3.2.0
> Reporter: Harsh J
> Assignee: Harsh J
> Priority: Trivial
> Attachments: OOZIE-822.patch
>
>
> In HiveMain.java, there is some code that does 'OutputStream os = new
> FileOutputStream("hive-site.xml");'. This indicates that running HiveMain
> will make it create a hive-site.xml in the launcher-mappers' working
> directory itself.
> Now if a user has <job-xml> set to a HDFS file named "hive-site.xml" too, it
> will create a symlink of this file in the working directory before the
> launcher task begins. In insecure mode this isn't an issue cause the
> LauncherMapper runs as the same user as the TT and will overwrite this file
> when it runs the above mentioned code. However, since distributed cache
> symlinks are owned by the TT-running user (mapred, say), in secure MR mode
> the LauncherMapper runs as the actual user and the code runs into a
> permission issue as it can't overwrite a file it does not own.
> We should hence document that one should not pass such a filename into the
> workflow that would make it symlink to work directory, to help avoid such a
> conflict.
> I'll think of the right words to put these in crisply and open up a review
> request.
--
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
