[
https://issues.apache.org/jira/browse/FALCON-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333095#comment-14333095
]
Pallavi Rao commented on FALCON-1041:
-------------------------------------
I agree that there is no uniformity in behaviour. When a user schedules a
process with validity end in the past, it is allowed and the process is
scheduled. But, when a user attempts an update with validity end in the past,
it fails.
I'm not completely aware of the historical background for this, but, I can only
try and guess. The reason for this behaviour could be that Oozie coordinator
itself allows end date in the past and replaces it with "now" and clears off
all the "backlog" by scheduling appropriate number of instances. When you are
updating such a process, there is no point is continuing to specify the end
date in the past as all the "backlog" has already been cleared.
> 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)
