You have to describe in detail what "taking a huge performance hit" means, there's not much to go on here...
But in general, adding N elements to a mutli-valued field isn't a problem at all. This bit of code: Document D = searcher.doc(hits[i].doc); is very suspicious. Does your cLucene version have lazy loading enabled and your Java version? Compression? How many hits are you cycling this way? How long does the search take as opposed to the above loop? Details please. Best Erick On Mon, Mar 7, 2011 at 6:41 AM, suman.holani <suman.hol...@zapak.co.in> wrote: > Hello, > > > > I am facing an issue for multivalued fields in lucene > > > > I am generating lucene doc , where page is multivalued . > > So my doc will be like this having more than n fields( which can be more > than 1500 also ..) per doc in case page attribute > > > > > > > > Example > > > <doc> > <media> > <id>12345</id> > <title>A title</title> > <description>My description</description> > <page> > <!-- The page element can > contain up to 15000 entries!!!! --> > > page1 > > Page 2 . > . > .n > > > </page> > > </media> > > > > > > </doc> > > > > > > > Will this structure can give a performance hit..?? as number of fields ar > dynamic for every doc..and can be huge. > > > > > > > > Actually I am using same structure in clucene and its running awesome. Bt > lucene , is taking huge performance hit > > Specially in . "Document D = searcher.doc(hits[i].doc); " > > > > > > Regards > > Suman > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
