falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peeyush Bishnoi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1343) validation of read/write endpoints is not reliable
Date Tue, 15 Sep 2015 16:05:45 GMT

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

Peeyush Bishnoi commented on FALCON-1343:

Actually I meant to say that instead of using static path "/tmp" directly in the patch, get
the "temp" value("/tmp") pointed by locations->location->temp used in cluster entity
for validation.
    <location name="staging" path="/projects/falcon/staging"/>
    <location name="temp" path="/tmp"/>
    <location name="working" path="/projects/falcon/working"/>

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

View raw message