First, kudos for making this test and attaching it. If nothing else that
makesme curious to see whether I really understand what's going on or not.
I think you're looking at the wrong tab in Luke ... I modified your test
to
write to an FSDir. When you look at the "overview" tab, you'll see three
t
I buy your theory that StandardAnalyzer is breaking up the stream, and that
this might be an indexing issue, rather than a query issue. When I look at
my index in Luke, as far as I can tell the literal (Parenth+eses is stored,
not the broken up tokens. Also, I can't seem to find an Analyzer that
I suspect that what's happening is that StandardAnalyzer is breaking
your stream up on the "odd" characters. All escaping them on the
query does is insure that they're not interpreted by the parser as (in
this case), the beginning of a group and a MUST operator. So, I
claim it correctly feeds (Pare
Say I have a book title, literally:
(Parenth+eses
How would I do a search to find exactly that book title, given the presence
of the ( and + ? QueryParser.escape isn't working.
I would expect to be able to search for (Parenth+eses [exact match] or
(Parenth+e [partial match]
I can use QueryPars
