Forward slash is now reserved for regular expression terms.
For the full list, see the Javadoc, here:
http://lucene.apache.org/core/4_0_0/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#Escaping_Special_Characters
I don't know of any change related to apostrophe. That may be token
filter-specific. Maybe related to possessive removal. In what context is it
a problem?
-- Jack Krupansky
-----Original Message-----
From: Shawn Heisey
Sent: Wednesday, November 28, 2012 11:52 AM
To: solr-user@lucene.apache.org
Subject: Solr4 - new characters requiring backslash escape?
I've been putting a new Solr 4.1 deployment through extensive testing
before we upgrade from 3.5.
My testing has turned up two characters that used to work fine with no
escaping that now give syntax errors without a preceding backslash.
Those characters are forward slash and apostrophe (single quote).
Is there a canonical list of characters that require backslashes to work
properly? I know about some already, such as parens and brackets.
On the same subject, but far less important because with SolrJ I don't
think I have to worry about it, is there a list of characters that
require URL encoding (%XX)?
Thanks,
Shawn
