[
https://issues.apache.org/jira/browse/FALCON-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518347#comment-14518347
]
Sowmya Ramesh commented on FALCON-1162:
---------------------------------------
[~me.venkatr]: Latest patch provided has check style violations. Please build
using "export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m -noverify" && mvn
clean verify -Phadoop-2,test-patch"
{noformat}
[INFO] Starting audit...
/Users/sramesh/Workspace/ApacheCommit/common/src/test/java/org/apache/falcon/entity/parser/ClusterEntityParserTest.java:323:
First sentence should end with a period.
Audit done.
{noformat}
> Cluster submit succeeds when staging HDFS dir does not have 777 (ALL)
> permission
> ---------------------------------------------------------------------------------
>
> Key: FALCON-1162
> URL: https://issues.apache.org/jira/browse/FALCON-1162
> Project: Falcon
> Issue Type: Bug
> Components: common
> Affects Versions: 0.6
> Reporter: Venkat Ramachandran
> Assignee: Venkat Ramachandran
> Priority: Blocker
> Fix For: 0.6.1
>
> Attachments: FALCON-1162.5.patch, falcon-1162.1.patch,
> falcon-1162.2.patch, falcon-1162.3.patch
>
>
> Staging HDFS dir specified in the cluster definition should have WORLD
> WRITABLE permission. It seems Cluster entity submit used to validate this
> condition in order to avoid further runtime failures.
> But, this check had been reverted as part of the FALCON-910 commits (only
> checks for 755) as below:
> ClusterEntityParser.java
> {code}
> checkPathOwnerAndPermission(cluster.getName(),
> stagingLocation.getPath(), fs, HadoopClientFactory.READ_EXECUTE_PERMISSION,
> false);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
