Try adding &debug=all to both records.

But these are very different queries. My guess is that
something _else_ changed, probably in solrconfig.xml
that's the cause, most probably your default field in your
3.6 case is the ID field. If that's the case you should
be able to change it in the 4.7 solnconfig.xml file for the
request handlers involved. One change is that you used
to be able to define this in schema.xml, but that's
been deprecated.

The first query parses as
ID:AFLGWBDAB <http://solr-dev.ss.com/solr/hotel/select/?q=ID:AFLGWBDAB> OR
default_search_field:AFLGWBGIB OR
default_search_field:FLGWGNDG

Best,
Erick



On Wed, Jul 23, 2014 at 2:51 AM, shashi.rsb <shashi....@hotmail.com> wrote:

> Hi,
>
>  Our backend application queries solr to retrieve certain records.
>
> We were initially on 3.6 version and now upgrade to 4.7 solr version.
>
> something has changed in terms of query string which needs a parentheses
> for
> the below query
>
> both the queries are from 4.7 solr.
>
> returns 1 record
> http://solr-dev.ss.com/solr/hotel/select/?q=ID:AFLGWBDAB OR AFLGWBGIB OR
> FLGWGNDG
>
> returns 14 records as expected.
>
> http://solr-dev.ss.com/solr/hotel/select/?q=ID:(AFLGWBDAB OR AFLGWBGIB OR
> FLGWGNDG)
>
>
> If you notice I had to add parentheses to get expected records.
>
> Also I cannot change the application code now as the release process to the
> application will go beyond 1 month. Is there a workaround within solrconfig
> to not use parentheses in 4.7
>
> Thanks
> Shashi
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/solr-3-6-to-4-7-upgrade-has-changed-the-query-string-tp4148719.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>

Reply via email to