But this is not the same - Lucene makes it transparent for you whether you have one or several field entries for one attribute. The behaviour will be the same in both of these cases:
Lucene document entry: attName: "term1 term2" attName: "term3 term4" or attName: "term1 term2 term3 term4" For the 1:n behaviour, you need some kind of logical 'grouping' of one dataset. whereby a query 'term1 term4' should NOT match, 'term1 term2' must match. Stefan Trcek schrieb: > On Wednesday 12 November 2008 14:58:53 Christian Reuschling wrote: >> In order to offer some simple 1:n matching, currently we create >> several, counted attributes and expand our queries that we search >> inside each attribute, e.g.: > > I use one attribute (Field) multiple times. > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
signature.asc
Description: OpenPGP digital signature