I need to analyze these values since I also want the benefits porterStemmer. The problem with using PhraseQuery is that I don't always know the slop. I may have values like "value4 ddd aaa". It's a tricky problem because I think Lucene sees all these values as one long value for the field "option".
-----Original Message----- From: Jake Mannix [mailto:[email protected]] Sent: Monday, October 12, 2009 1:25 PM To: [email protected] Subject: Re: querying multi-value fields Or else just make sure that you use PhraseQuery to hit this field when you want "value1 aaa". If you don't tokenize these pairs, then you will have to do prefix/wildcard matching to hit just "value1" by itself (if this is allowed by your business logic). -jake On Mon, Oct 12, 2009 at 1:21 PM, Adriano Crestani <[email protected] > wrote: > Hi Eric, > > To achieve what you want, do not tokenize the values you query/add to this > field. > > On Mon, Oct 12, 2009 at 4:05 PM, Angel, Eric <[email protected]> wrote: > > > I have documents that store multiple values in some fields (using the > > document.add(new Field()) with the same field name). Here's what a > > typical document looks like: > > > > > > > > doc.option="value1 aaa" > > > > doc.option="value2 bbb" > > > > doc.option="value3 ccc" > > > > > > > > I want my queries to only match individual values, for example, a query > > for "value2 bbb" would return the above document, but a query for > > "value1 ccc" should not. Is this at all possible in lucene at query > > time? Could payloads be used for this? > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
