falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pallavi Rao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-816) Fallback to Falcon FileSystem (logged in user) when ACL is not available in LogCleanupService
Date Thu, 05 Mar 2015 05:53:38 GMT

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

Pallavi Rao commented on FALCON-816:
------------------------------------

The fallback option may be required for backward compatibility reason at least (from 0.5 to
0.6). See FALCON-1063

> 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: Bug
>          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)

Mime
View raw message