I don't understand why the compressed fields are not just handled externally in the Document class - just add uncompress/compress methods. This way all Lucene needs to understand is binary fields, and you don't have any of these problems during merging or initial indexing.
This is an excellent point. Since these are just stored fields, why not have Lucene treat them as [opaque] binary fields so they are not touched during normal index operations. And then only when a Document really needs to provide this value, it would decompress then?
Was there a counterbalance that justified having the compress logic inside the indexing code?
Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
