Yes, there is. But since the real query is very long and complex per core, I don't want each core to work very hard on irrelevant query parts of other cores. Perhaps I can write some query plugin which will strip the unnecessary parts on each core? Thanks, Avner
-----Original Message----- From: Jack Krupansky [mailto:j...@basetechnology.com] Sent: Wednesday, May 21, 2014 6:52 PM To: solr-user@lucene.apache.org Subject: Re: Distributed Search in Solr with different queries per shard Unfortunately the same query will be sent to all cores if you use the shards parameter to query multiple cores. Is there some characteristic of the first core that is distinct from the second core so that you could OR the differences between the two? -- Jack Krupansky -----Original Message----- From: Avner Levy Sent: Wednesday, May 21, 2014 9:56 AM To: solr-user@lucene.apache.org Subject: Distributed Search in Solr with different queries per shard 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. Email secured by Check Point