The compound index structure is meant for indexes with a large number of fields. I was watching the files in the index directory of my compound index while it was being optimized. The IndexWriter that I used was set to use compound file. It looks to me that Lucene first combined all existing segments into a new multifile segment, then it converted this multifile segment into the compound format. So I think the data for the entire index is actually being written to disk twice. Is there any way to configure Lucene to write the data once only into a compound segment without first writing a multifile segment first?
Bill On Apr 4, 2005 6:40 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote: > They are all indexed (and they all need to be under the current design). > > -Yonik > > On Apr 4, 2005 6:16 PM, Doug Cutting <[EMAIL PROTECTED]> wrote: > > Yonik Seeley wrote: > > > I know Lucene is very scalable in many ways, but how about number of > > > fieldnames? > > > > > > We have an index using around 6000 unique fieldnames, > > > > How many of these fields are indexed? At this point I would recommend > > against having more than a handful of indexed fields. If the fields are > > only stored, then it shouldn't make much difference. > > > > Doug > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
