Thanks Erick & Shawn, I will analyze with your input and share outcome.
Thanks Ravi -----Original Message----- From: Erick Erickson [mailto:erickerick...@gmail.com] Sent: Thursday, July 10, 2014 12:17 AM To: solr-user@lucene.apache.org Subject: Re: Lower/UpperCase Issue Side note. Puttling LowercaseFilter in front of WordDelimiterFilterFactory is usually a poor choice. One of the purposes of WDFF is that it breaks lower->upper case transitions into separate tokens. NOTE: This is _not_ germane to your problem IMO. But it _is_ an indication that you might want to spend some time with the admin/analysis page to understand the affects of the filters on various inputs. Also, add &debug=all to your query to see exactly why things were returned in the order they were. In this case, as Shawn says, all queries will be scored the same. Actually, I'd be very interested in the output of adding &debug=all to the two queries. Theoretically, since all the scores are the same, I'd expect the returns to be constantly ordered unless the filter query is parsing Balancer and BALANCER differently. I'm going to guess that the parsing of the fq clause is different somehow, but that's only a guess. Best, Erick On Wed, Jul 9, 2014 at 4:20 PM, Shawn Heisey <s...@elyograg.org> wrote: > On 7/9/2014 2:02 PM, EXTERNAL Taminidi Ravi (ETI, > Automotive-Service-Solutions) wrote: >> Here is the schema part. >> >> <field name="Name" type="text_general" indexed="true" stored="true" >> /> > > Your query is *:*, which is a constant score query. You also have a > filter, which does not affect scoring. > > Since there is no score difference between different documents with > your query results, the lack of a sort parameter means that you will > most likely get the results in the order that Lucene returns them, > which is completely indeterminate. > > There's probably some minute difference between the two queries at the > Lucene level, possibly because the stemmer behaves differently with > different case or just because the internal matching happens > differently, which makes Lucene return the results in a different order. > > If you want to be absolutely in control of your result order when the > query results in a constant score, you'll need to specify a sort parameter. > > Thanks, > Shawn >
