falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-677) Feed data and stats path defaults to /tmp/
Date Mon, 08 Sep 2014 07:08:28 GMT

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

Ajay Yadav commented on FALCON-677:

Will assuming a unique default path for each feed in /tmp(something like /tmp/feed-name/stats/)
be a bad idea?

> 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
>         Attachments: 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