I'm trying to decide whether attacking the underlying issue of RangePartitioner running eager jobs in rangeBounds (i.e. SPARK-1021) is a better option than a messy workaround for some async job-handling stuff that I am working on. It looks like there have been a couple of aborted attempts to solve the problem, but no solution or clear path to one at this point.
Has anybody made any further progress or does anyone have any new ideas on how to proceed?
