Aperiodic Data handling in oozie

Currently Oozie scheduling works on periodic datasets. It does not have any mechanism to handle aperiodic datasets, which doesn’t follow a fixed schedule/frequency.

Use cases
When incoming dataset arrives with no fixed schedule.
Need to trigger the job based all data available since last run with a possible cap on the max size to process in one run.
Try to avoid creating so many instances when you know input instances will be very few.