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-1343) validation of read/write endpoints is not reliable
Date Wed, 16 Sep 2015 04:56:45 GMT

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

Pallavi Rao commented on FALCON-1343:
-------------------------------------

[~bvellanki], validation of whether we can read from HDFS happens as part of validateLocations.
Also, write gets validated because we copy libraries to working path (SharedLibraryHostingService
does it). So, although the validation does not happen as part validateInterface, it does happen.
The submit fails if we cannot read/write to HDFS.

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

Mime
View raw message