The current implementation makes some assumptions, such as the "unique key" is a single field, not any sort of compound key, and it doesn't allow deletes by query. That, coupled with a more complex implementation makes me wary of putting it in IndexWriter.
By "current implementation", you meant Lucene IndexReader in general, right?
I'll rephrase my original question: When implementing NewIndexModifier, what type of efficiencies do we get by using the new protected methods of IndexWriter vs using the public APIs of IndexReader and IndexWriter?
What do you think can be best achieved by using the public APIs of IndexReader and IndexWriter? Regards, Ning --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
