[
https://issues.apache.org/jira/browse/FALCON-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149633#comment-14149633
]
Venkatesh Seetharam commented on FALCON-752:
--------------------------------------------
bq. Am assuming the staging & working dirs are still owned by falcon, but are
world readable. Please confirm. Would like to have notes relating to this in
the docs for user reference.
This is overridden in FALCON-753
bq. Can we use HadoopClientFactory instead of directly creating a file system
object ?
Somehow the files are owned by yarn if I use UGI.getCurrentUser() and hence
used this
bq. Perhaps an unintentional wrap around
Agreed
bq. JobLogMover: How will this work? This is actually executing as the process
or feed owner. If falcon working/staging dir is not 777, how would they be able
to write to this? Please clarify, this might be a blocker
Srikanth, this is copied into logs dir and its 777.
> Override the permissions for staging and working dirs with 755
> --------------------------------------------------------------
>
> Key: FALCON-752
> URL: https://issues.apache.org/jira/browse/FALCON-752
> Project: Falcon
> Issue Type: Sub-task
> Components: oozie
> Affects Versions: 0.6
> Reporter: Venkatesh Seetharam
> Assignee: Venkatesh Seetharam
> Fix For: 0.6
>
> Attachments: FALCON-752.patch
>
>
> This would only implement phase-1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
