> Yonik mentioned this in email. It does sound like a better place for > this might be in a higher level class. IndexWriter would really not > be just a writer/appender once delete functionality is added to it, > even if it's the IndexReaders behind the scenes doing the work. So > if you are going to be redoing the patch, consider this.
Interesting. I thought a writer should support both inserts and deletes. > Perhaps IndexModifier methods should be deprecated and it should get > a new/your API? Do you mention putting the patch in IndexModifier? I'm fine with that. Is it ok if the new IndexModifier extends IndexWriter, since they do share most of the APIs and implementations? Regards, Ning --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
