[OOZIE-1976] Specifying coordinator input datasets in more logical ways

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk
• Fix Version/s: 4.3.0
• Component/s: coordinator
• Assignee: Purshotam Shah
• Reporter: Mona Chitnis
• Created: 18/Aug/14 21:14
• Updated: 11/Aug/17 23:35
• Resolved: 27/May/16 23:08

Description

All dataset instances specified as input to coordinator, currently work on AND logic i.e. ALL of them should be available for workflow to start. We should enhance this to include more logical ways of specifying availability criteria e.g.

• OR between instances
• minimum N out of K instances
• delta datasets (process data incrementally)

Use-cases for this:

• Different datasets are BCP, and workflow can run with either, whichever arrives earlier.
• Data is not guaranteed, and while $coord:latest allows skipping to available ones, workflow will never trigger unless mentioned number of instances are found.
• Workflow is like a ‘refining’ algorithm which should run after minimum required datasets are ready, and should only process the delta for efficiency.

This JIRA is to discuss the design and then the review the implementation for some or all of the above features.

Issue Links

• breaks: OOZIE-3031 Coord job with only unresolved dependencies doesn't timeout
• links to: RB