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-1041) Updating feed's data path doesn't create a new bundle for the dependent process.
Date Fri, 20 Feb 2015 10:12:12 GMT

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

Pallavi Rao commented on FALCON-1041:

[~karishmag9], as discussed, it works in my dev. environment when I update the feed location:
pallavi.rao$ bin/falcon entity -type feed -update -file examples/entity/filesystem/in-feed.xml
-name in
falcon/update/default/Updated successfully(feed) in/Effective Time: 2015-02-20T09:26Z. Old
bundle id: 0000082-150216152436391-oozie-oozi-C. New bundle id: 0000092-150216152436391-oozie-oozi-B
(process) pig-process/Effective Time: 2015-11-15T00:05Z. Old bundle id: 0000090-150216152436391-oozie-oozi-C.
New bundle id: 0000096-150216152436391-oozie-oozi-B

May be it is some corner case, please verify with the latest codebase and provide further
details. One case where I can think of when the process bundle doesn't get updated is when
the cluster validity in the process definition is before the current date, which means the
process shouldn't run anyway.

> Updating feed's data path doesn't create a new bundle for the dependent process. 
> ---------------------------------------------------------------------------------
>                 Key: FALCON-1041
>                 URL: https://issues.apache.org/jira/browse/FALCON-1041
>             Project: Falcon
>          Issue Type: Bug
>          Components: feed, process
>    Affects Versions: trunk
>         Environment: QA
>            Reporter: Karishma Gulati
> A user schedules feedA and schedules a process, processA which has input feed feedA.
The user then updates data path of feedA. New feed bundle is created. However, a new process
bundle is not created.  

This message was sent by Atlassian JIRA

View raw message