On 02/04/2010 at 3:24 PM, Chris Hostetter wrote:
> : Since phrase query terms aren't analyzed, you're getting exact
> : matches
>
> quoted phrase passed to the QueryParser are analyzed -- but they are
> analyzed as complete strings, so Analyzers that treat whitespace
> special may produce differne
: Since phrase query terms aren't analyzed, you're getting exact matches
quoted phrase passed to the QueryParser are analyzed -- but they are
analyzed as complete strings, so Analyzers that treat whitespace special
may produce differnet Terms then if the individual "words" were analyzed
indiv
Hi Jamie,
Since phrase query terms aren't analyzed, you're getting exact matches for
terms "было" and "время", but when you search for them individually, they are
analyzed, and it is the analyzed query terms that fail to match against the
indexed terms. Sounds to me like your index-time and qu
There is no pseudo field for all search terms. 2 common practices are
to use MultiFieldQueryParser or to add a catch-all field. I tend to
do the latter.
At a glance I'd agree that the second query should also return 48
hits. Maybe a small self-contained test case or standalone program
would be
I believe you must capitalize the AND. lower-case 'and' is ignored.
you could also construct your own BoolenQuery if you wanted.
I recommend copy of Luke to interactively examine how queries
are parsed. Also, toString is your friend
Best
Erick
On Fri, Apr 4, 2008 at 9:41 AM, Jamie <[EMAI
I would also like to point out that we also thought about using a filter
but it is being used for other things.
Jamie wrote:
Hi there
I need some help in understanding Lucene's query mechanism. I am
receiving unexpected query results when combining terms with AND and
OR operators. We are usi
