You could index both a compound field and the components separately. This could be simplified by sending the value in once as the compound format: review,1 Jan 2007 revision, 2 Jan 200 And then use a copyField with a regex tokenizer to extract and index the date into a separate field. You could index the type separately via the same mechanism.
-Yonik On 9/3/07, Bharani <[EMAIL PROTECTED]> wrote: > > Hi, > > I have got two sets of document > > 1) Primary Document > 2) Occurrences of primary document > > Since there is no such thing as "join" i can either > > a) Post the primary document with occurrences as multi valued field > or > b) Post the primary document for every occurrences i.e. classic > de-normalized route > > My problem with > > Option a) This works great as long as the occurrence is a single field but > if i had a group of fields that describes the occurrence then the search > returns wrong results becuase of the nature of text search > > i.e <date>1 Jan 2007</date> > <type> review</type> > > <date> 2 Jan 2007 </date> > <type> revision</type> > > if i search for 2 Jan 2007 and <date> 1 Jan 2007 </date> i will get a hit > (which is wrong) becuase there is no grouping of fields to associate date > and type as one unit. If i merge them as one entity then i cant use the > range quieries for date > > Option B) This would result in large number of documents and even if i try > with index only and not store i am still have to deal with duplicate hit - > becuase all i want is the primary document > > > Is there a better approach to the problem? > > Thanks > Bharani > > > -- > View this message in context: > http://www.nabble.com/Multiple-Values--Structured--tf4370282.html#a12456399 > Sent from the Solr - User mailing list archive at Nabble.com. > >
