I suppose you could, but I _really_ question whether it's a wise investment in time. Personally I'd treat them as two different collections and have the app layer fire off two queries and do the aggregation (this is a variant of "federated search" I think). This removes your issue with having the cores "do extra work"....
Additionally, I'd really prove out that the "extra work" is actually a measurable performance issue before worrying about this, it smells like premature optimization. FWIW, Erick On Wed, May 21, 2014 at 6:56 AM, Avner Levy <av...@checkpoint.com> wrote: > I have 2 cores. > One with active data and one with historical data (for documents which were > removed from the active one). > I want to run Distributed Search on both and get the unified result (as > supported by Solr Distributed Search, I'm not using Solr Cloud). > My problem is that the query for each core is different. > Is there a way to specify different query per core and still let Solr to > unify the query results? > For example: > Active data core query: select all green docs > History core query: select all green docs with year=2012 > Is there a way to extend the distributed search handler to support such a > scenario? > Thanks in advance, > Avner > ยท One option is to send a unified query to both but then each core > will work harder for no reason. >
