Re: Query Elevation exception on shard queries

2013-05-08 Thread varun srivastava
Ok found the solution .. Like SpellcheckComponent , Elevate Component also requires shards.qt param .. But still dont know why both these components doesn't work in absense of shards.qt . Can anyone explain ? Thanks Varun On Mon, May 6, 2013 at 1:14 PM, varun srivastava

Re: Query Elevation exception on shard queries

2013-05-06 Thread Ravi Solr
Varun, Since our cores were totally disjoint i.e. they pertain to two different applications which may or may not have results for a given query, we moved the elavation outside of solr into our java code. As long as both cores had some results to return for a given query elevation would

Re: Query Elevation exception on shard queries

2013-05-06 Thread varun srivastava
Thanks Ravi. So then it is a bug . On Mon, May 6, 2013 at 12:04 PM, Ravi Solr ravis...@gmail.com wrote: Varun, Since our cores were totally disjoint i.e. they pertain to two different applications which may or may not have results for a given query, we moved the elavation outside

Re: Query Elevation exception on shard queries

2013-05-04 Thread varun srivastava
Hi Ravi, I am getting same probelm . You got any solution ? Thanks Varun On Fri, Mar 29, 2013 at 11:48 AM, Ravi Solr ravis...@gmail.com wrote: Hello, We have a Solr 3.6.2 multicore setup, where each core is a complete index for one application. In our site search we use sharded query

Re: Query Elevation exception on shard queries

2013-05-04 Thread varun srivastava
Hi , I am getting same exception as Ravi when using shard query containing elevated terms. I am using solr 4.0.0 stable version which is suppose to contain fix for this. https://issues.apache.org/jira/browse/SOLR-2949 ava.lang.IndexOutOfBoundsException: Index: 1, Size: 0\n\tat

Query Elevation exception on shard queries

2013-03-29 Thread Ravi Solr
Hello, We have a Solr 3.6.2 multicore setup, where each core is a complete index for one application. In our site search we use sharded query to query two cores at a time. The issue is, If one core has docs but other core doesn't for an elevated query solr is throwing a 500 error. I woudl