lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Lackhoff <mich...@lackhoff.de>
Subject Re: Is semicolon a character that needs escaping?
Date Wed, 08 Sep 2010 06:16:48 GMT
On 08.09.2010 00:05 Chris Hostetter wrote:

> 
> : Subject: Is semicolon a character that needs escaping?
> 	...
> : >From this I conclude that there is a bug either in the docs or in the
> : query parser or I missed something. What is wrong here?
> 
> Back in Solr 1.1, the standard query parser treated ";" as a special 
> character and looked for sort instructions after it.  
> 
> Starting in Solr 1.2 (released in 2007) a "sort" param was added, and 
> semicolon was only considered a special character if you did not 
> explicilty mention a "sort" param (for back compatibility)
> 
> Starting with Solr 1.4, the default was changed so that semicolon wasn't 
> considered a meta-character even if you didn't have a sort param -- you 
> have to explicilty select the "lucenePlusSort" QParser to get this 
> behavior.
> 
> I can only assume that if you are seeing this behavior, you are either 
> using a very old version of Solr, or you have explicitly selected the 
> lucenePlusSort parser somewhere in your params/config.
> 
> This was heavily documented in CHANGES.txt for Solr 1.4 (you can find 
> mention of it when searching for either ";" or "semicolon")

I am using 1.3 without a sort param which explains it, I think. It would
be nice to update to 1.4 but we try to avoid such actions on a
production server as long as everything runs fine (the semicolon thing
was only reported recently).

Many thanks for your detailed explanation!
-Michael

Mime
View raw message