You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2017/03/08 12:13:38 UTC

[jira] [Resolved] (OOZIE-822) Document that the Oozie Hive action creates a "hive-site.xml" file in the task's working directory

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

Harsh J resolved OOZIE-822.
---------------------------
    Resolution: Not A Problem

With recent improvements in the way YARN NodeManagers localize files, this is no longer a problem in secure clusters (file is owned by the right user, so overwrites work fine).

> 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 was sent by Atlassian JIRA
(v6.3.15#6346)