[
https://issues.apache.org/jira/browse/FALCON-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Yadava updated FALCON-1605:
--------------------------------
Summary: Instance API is not working as expected in case of Native
Scheduler (was: Instance Api's working not as expected in case of Native
Scheduler )
> Instance API is not working as expected in case of Native Scheduler
> --------------------------------------------------------------------
>
> Key: FALCON-1605
> URL: https://issues.apache.org/jira/browse/FALCON-1605
> Project: Falcon
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: pavan kumar kolamuri
> Assignee: pavan kumar kolamuri
> Fix For: 0.9
>
> Attachments: FALCON-1605.patch
>
>
> Generally all instance api's will take start and end time w.r.t to nominal
> time. But with new Falcon Scheduler start time and end time are considered
> w.r.t to actual start time and end time of workflow which leads to
> incompatible change.
> {noformat}
> falcon instance -type process -name ProcessName -status -start
> 2015-11-16T04:00Z -end 2015-11-16T04:01Z
> should give output of process instance of nominal time 2015-11-16T04:00Z
> o/p : Instances:
> Instance Cluster SourceCluster Status
> Start End Details Log
> -----------------------------------------------------------------------------------------------
> 2015-11-16T04:00Z local-cluster - SUCCEEDED
> 2015-11-16T04:06Z 2015-11-16T04:13Z -
> http://localhost:11000/oozie?job=0113052-151104055028899-oozie-oozi-W
> actions:
> enhance SUCCEEDED
> http://localhost:8088/proxy/application_1446613735384_1027046/
> but with new falcon scheduler it is not giving any output since workflow
> started later at 2015-11-16T04:06Z.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
