[
https://issues.apache.org/jira/browse/FALCON-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745544#comment-14745544
]
Balu Vellanki commented on FALCON-1343:
---------------------------------------
[~peeyushb] /tmp always exists in HDFS, not so for /temp. For readonly, Falcon
do not need to create any files. Falcon just has to verify that user can
connect to namenode. So /tmp is better option.
> validation of read/write endpoints is not reliable
> --------------------------------------------------
>
> Key: FALCON-1343
> URL: https://issues.apache.org/jira/browse/FALCON-1343
> Project: Falcon
> Issue Type: Sub-task
> Components: general
> Reporter: Balu Vellanki
> Assignee: Balu Vellanki
> Attachments: FALCON-1343.patch
>
>
> A read/write endpoint is currently validated by creating a filesystem with
> the endpoint url.
> {code}
> HadoopClientFactory.get().createProxiedFileSystem(conf);
> {code}
> I confirmed with a HDFS team member that it is not sufficient validation.
> Ideally check if the end user has access by doing atleast a list /tmp call
> after creating proxiedFileSystem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
