On Tue, Nov 10, 2009 at 1:18 PM, Michael Busch <busch...@gmail.com> wrote:
> I talked to Marvin on ApacheCon; in Lucy he wants to have all the compound > file support in the store package, separately from the indexer. I think that > would make sense in Lucene too, there's not really the need to have it > tightly integrated in the IndexWriter and SegmentMerger. We can generalize > the compound file concept further, so that with parallel indexes the files > can be selected in either direction for inclusion in a compound file. > > E.g. if we separated the inverted index and store, so that they are > logically two parallel index components, then the .cfx file as it works now > would contain files from two parallel index components (term vectors from > inverted index, stored fields from the store). This is fine if you don't > want to update those components individually and can remain this way for the > default IndexWriter implementation. But if we generalize the compound > concept, then people can alter this behavior to better suit their update > requirements. > > I think this would actually be a very clean design (even though it might > sound complicated here). This sounds great! Mike --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
