[
https://issues.apache.org/jira/browse/FALCON-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333085#comment-14333085
]
Karishma Gulati commented on FALCON-1041:
-----------------------------------------
Yes, you are right, the validity of the cluster in the process definition was
in the past. So, for a process with cluster validity before the previous date,
this is what happened :
Upon scheduling, bundles and coordinators for both the feed and process were
created. However upon feed update, only the bundle for the feed was created.
This, in my opinion is slightly contradictory behaviour. Especially in a
scenario where say a user A scheduled a process with old cluster validity (he
would see bundles for both the feed and the process), and a user B updated the
feed. The process would no longer exist for user A after feed updation, which
won't be a desired result for him.
> 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
(v6.3.4#6332)
