Re: Lucene QueryParser/Analyzer inconsistency

2014-06-19 Thread Luis Pureza
f:one f:two as expected. However, if I change the text to "hello one/two", I get: f:hello f:one/two I can't figure out what's going on. My custom tokenizer seems to work well, but I'd rather use Lucene's built-ins. Thank you, Luis On Wed, Jun 18, 2014 at

Re: Lucene QueryParser/Analyzer inconsistency

2014-06-18 Thread Luis Pureza
, just try a simple, unescaped slash in your char mapping table. > > -- Jack Krupansky > > -Original Message- From: Luis Pureza > Sent: Tuesday, June 17, 2014 1:43 PM > To: java-user@lucene.apache.org > Subject: Lucene QueryParser/Analyzer inconsistency > > > Hi,

Lucene QueryParser/Analyzer inconsistency

2014-06-17 Thread Luis Pureza
Hi, I'm experience a puzzling behaviour with the QueryParser and was hoping someone around here can help me. I have a very simple Analyzer that tries to replace forward slashes (/) by spaces. Because QueryParser forces me to escape strings with slashes before parsing, I added a MappingCharFilter