You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@falcon.apache.org by "Venkatesh Seetharam (JIRA)" <ji...@apache.org> on 2014/11/07 20:42:35 UTC

[jira] [Commented] (FALCON-816) Fallback to Falcon FileSystem (logged in user) when ACL is not available in LogCleanupService

    [ https://issues.apache.org/jira/browse/FALCON-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202535#comment-14202535 ] 

Venkatesh Seetharam commented on FALCON-816:
--------------------------------------------

Moving this out of 0.6.

> Fallback to Falcon FileSystem (logged in user) when ACL is not available in LogCleanupService
> ---------------------------------------------------------------------------------------------
>
>                 Key: FALCON-816
>                 URL: https://issues.apache.org/jira/browse/FALCON-816
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: oozie
>    Affects Versions: 0.6
>            Reporter: Venkatesh Seetharam
>
> I do not agree this should be the behavior as the umask can be 077 and the logged in user, falcon, may not have access to delete the contents in the logs dir. But, [~shwethags] thinks there should be a fallback option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)