[
https://issues.apache.org/jira/browse/FALCON-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066404#comment-15066404
]
pavan kumar kolamuri commented on FALCON-1681:
----------------------------------------------
[~pragya.mittal] Yes makes sense, Lets fix this in NativeScheduler and we can
create another jira to fix the existing one through oozie. But i have seen few
jira's where this is already discussed, if there is issue in doing this please
let us know.
> Native scheduler does not maintain idempotent behaviour while scheduling
> entities.
> ----------------------------------------------------------------------------------
>
> Key: FALCON-1681
> URL: https://issues.apache.org/jira/browse/FALCON-1681
> Project: Falcon
> Issue Type: Bug
> Components: scheduler
> Affects Versions: 0.9
> Reporter: Pragya Mittal
>
> Currently if an entity is scheduled once, user can schedule that entity any
> number of times. Since scheduler is not changing any functionality for end
> users, it should show the same behaviour. Although when a scheduled entity is
> scheduled again it fails with the following error :
> {noformat}
> dataqa@lda01:/mnt/users/pragya/scheduler$ fep -schedule -name Native-2
> -properties falcon.scheduler:oozie
> ERROR: Bad Request;ua1/Entity schedule failed for process: Native-2
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
