As always, the best things to do are to know exactly what you indexed
(AnalyzerDemo from Lucene in Action helps here, and of course the
wonderful tool, Luke). Then try simplifying your query to a
TermQuery for a term you know or suspect you indexed. QueryParser
introduces a lot of variabl
On 12/20/05, John Powers <[EMAIL PROTECTED]> wrote:
> Ok, I understand the .toString() part.
>
> But, if I have some 19" in the text of these items, and I do a search with
> 19", that has been escaped before parsingwhy am I not getting anything?
> The indexer analyzer took them out? So then t
Ok, I understand the .toString() part.
But, if I have some 19" in the text of these items, and I do a search with
19", that has been escaped before parsingwhy am I not getting anything?
The indexer analyzer took them out? So then to find these documents, I
would want to either change the ana
Here's more on query-parser escaping gotchas:
http://www.mail-archive.com/[email protected]/msg02354.html
-Yonik
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 12/20/05, John Powers <[EMAIL PROTECTED]> wrote:
> I would like to be able to search for 19 inches with the quote. So I get a
> query like this:
> Line 1: +( (name:19"*^4 ld:19"*^2 sd:19"*^3 kw:19"*^1) )
>
>
> That won't work, so I wanted to escape the quotes.The docs said to use a
> backs
I would like to be able to search for 19 inches with the quote. So I get a
query like this:
Line 1: +( (name:19"*^4 ld:19"*^2 sd:19"*^3 kw:19"*^1) )
That won't work, so I wanted to escape the quotes.The docs said to use a
backslash. So I'm doing this:
luceneQuery.toString().replaceAll("\"
