Re: Distributed Search in Solr with different queries per shard

2014-05-25 Thread Ramkumar R. Aiyengar
I agree with Eric that this is premature unless you can show that it makes a difference. Firstly why are you splitting the data into multiple time tiers (one recent, and one all) and then waiting to merge results from all of them? Time tiering is useful when you can do the search separately on bot

Re: Distributed Search in Solr with different queries per shard

2014-05-22 Thread Erick Erickson
014 6:13 PM > To: solr-user@lucene.apache.org > Subject: Re: Distributed Search in Solr with different queries per shard > > 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

RE: Distributed Search in Solr with different queries per shard

2014-05-21 Thread Avner Levy
[mailto:erickerick...@gmail.com] Sent: Wednesday, May 21, 2014 6:13 PM To: solr-user@lucene.apache.org Subject: Re: Distributed Search in Solr with different queries per shard I suppose you could, but I _really_ question whether it's a wise investment in time. Personally I'd treat them as two

RE: Distributed Search in Solr with different queries per shard

2014-05-21 Thread Avner Levy
ssage- 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

Re: Distributed Search in Solr with different queries per shard

2014-05-21 Thread Jack Krupansky
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--

Re: Distributed Search in Solr with different queries per shard

2014-05-21 Thread Erick Erickson
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 c

Re: Distributed Search in Solr

2009-07-14 Thread Sumit Aggarwal
Hi Grant, What i have got from your comments is: 1. We will have to add a support for BoostingTermQuery which extends SpanTermQuery like in lucene payload support. In current world we anyway have other class which is extending SpanTermQuery . Where should i put this class or newly built BoostingTe

Re: Distributed Search in Solr

2009-07-10 Thread Grant Ingersoll
On Jul 9, 2009, at 11:58 PM, Sumit Aggarwal wrote: Hi, 1. Calls made to multiple shards are made in some concurrent fashion or serially? Concurrent 2. Any idea of algorithm followed for merging data? I mean how efficient it is? Not sure, but given that Yonik implemented it, I suspect