[FALCON-1739] Tracking API differences between Native Scheduler and Oozie

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.9
• Component/s: oozie, scheduler
• Assignee: Unassigned
• Reporter: Pragya Mittal
• Created: 08/Jan/16 12:54
• Updated: 08/Jan/16 13:12

Description

Ideally end user should be unaware of the behaviour of API result irrespective of the scheduler choice. This is not the case as of now. There are some mismatch in the way scheduler (native vs oozie) shows the output. This JIRA is to track all those differences and reach a common consensus.

Issue Links

• requires: FALCON-1168 Native Scheduler in Falcon - Umbrella JIRA

Sub-Tasks

• Killed API response in case of succeeded instances: Open
• Rerun API behaviour different in case of succeeded instances: Resolved
• Different behaviour in instance materialization: Open