falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-677) Feed data and stats path defaults to /tmp/
Date Thu, 11 Sep 2014 05:22:33 GMT

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

Shwetha G S commented on FALCON-677:

You mean the check that DATA path is always specified for filesystem based feed? No, can't
be done in xsd as locations is a choice

> Feed data and stats path defaults to /tmp/
> ------------------------------------------
>                 Key: FALCON-677
>                 URL: https://issues.apache.org/jira/browse/FALCON-677
>             Project: Falcon
>          Issue Type: Bug
>          Components: feed
>            Reporter: Suhas Vasu
>            Assignee: Suhas Vasu
>             Fix For: 0.6
>         Attachments: FALCON-677-v2.patch, FALCON-677-v3.patch, FALCON-677-v4.patch, FALCON-677.patch
> If a feed does not have stats path specified, it assumes it as /tmp/ on the hdfs. Ideally
we should be throwing an error that the specified feed does not have a stats path.
> Users may have specified to delete the stats path if it exists, in the prepare tag in
workflow. In such a scenario the whole of /tmp/ is cleared, which is totally undesirable.

This message was sent by Atlassian JIRA

View raw message