Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
9.0
-
None
-
New
Description
Today, if a user of DrillSideways wants to provide their own CollectorManager when invoking search, they get this alternate, "concurrent" implementation that creates N copies of the provided DrillDownQuery (where N is the number of drill-down dimensions) and runs them all concurrently. This is a very different implementation than the one a user would get if providing a Collector instead. Additionally, an ExecutorService must be provided when constructing a DrillSideways instance if the user wants to bring their own CollectorManager (otherwise, they'll get an unfriendly NPE when calling search).
I propose adding an implementation to DrillSideways that will run the "non-concurrent" algorithm in the case that a user wants to provide their own CollectorManager but doesn't want to provide an ExecutorService (and doesn't want the concurrent algorithm).
Attachments
Issue Links
- links to