[
https://issues.apache.org/jira/browse/FALCON-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125271#comment-14125271
]
Suhas Vasu commented on FALCON-677:
-----------------------------------
Assuming any path is not advisable as it may be used by any other
hadoop-job/falcon-process leading to erroneous behavior.
> 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
(v6.3.4#6332)
