So is IndexModifier opening an IndexReader when someone calls .delete() then closing the reader and opening an IndexWriter when someone calls addDocument() (for example)?
Sounds like that could get fairly inefficient. Is IndexModifier for more convenience (and less performance) than using reader and writer separately? Thanks -mark This e-mail message, and any attachments, is intended only for the use of the individual or entity identified in the alias address of this message and may contain information that is confidential, privileged and subject to legal restrictions and penalties regarding its unauthorized disclosure and use. Any unauthorized review, copying, disclosure, use or distribution is strictly prohibited. If you have received this e-mail message in error, please notify the sender immediately by reply e-mail and delete this message, and any attachments, from your system. Thank you. -----Original Message----- From: Daniel Naber [mailto:[EMAIL PROTECTED] Sent: Friday, September 29, 2006 2:46 PM To: java-user@lucene.apache.org Subject: Re: IndexModifier and finding records On Friday 29 September 2006 14:54, Mark Modrall wrote: > It > would be nice if I could do IndexSearcher(IndexModifier) or > IndexSearcher(IndexModifier.getReader()) or something. The reader and writer are closed automatically if needed, so they cannot easily be given to the outside. If you want to give it a try anway: IndexModifer was designed to be extendable, so you can just create your own subclass of IndexModifier that adds these methods. Regards Daniel -- http://www.danielnaber.de --------------------------------------------------------------------- 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]
