ClientUtils.escapeQueryChars seems a bit aggressive to me in terms of what it escapes. It references http://lucene.apache.org/java/docs/queryparsersyntax.html#Escaping Special Characters, but doesn't explicitly escape them, instead opting for the more general \W regex. Thus, I'm noticing that chars that don't need to be escaped ( like / ) are being escaped.

Anyone recall why this is? I suppose the problem comes in when one considers other query parsers, but maybe we should just mark this one as explicitly for use w/ the Lucene QP?

-Grant

Reply via email to