[ https://issues.apache.org/jira/browse/LUCENE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535335 ]
Michael Busch commented on LUCENE-743: -------------------------------------- > in deciding "to clone or not clone" for the purposes of implementing > reopen, it may make sense to step back and ask a two broader questions... I agree! > 1) what was the motivation for approaching reopen using clones in the > first place Good summarization! You are right, I started the clone approach because IndexReaders are not "read only" objects. > "if reopen(closeOld=false) returns a new reader it will share state with > the current reader, attempting to do the following operations on this > new reader will result in undefined behavior" This would mean, that we simply warn the user that performing write operations with the re-opened indexreader will result in undefined behavior, whereas with Mike's approach we would prevent such an undefined behavior by using reference counting. Hmm, so what are our long-term plans for indexreaders? If our goal is to make them read-only (we can delete via IndexWriter already), then I think adding those warning comments to reopen(), as you suggest Hoss, would be sufficient. If everybody likes this approach I'll go ahead and submit a new patch. > IndexReader.reopen() > -------------------- > > Key: LUCENE-743 > URL: https://issues.apache.org/jira/browse/LUCENE-743 > Project: Lucene - Java > Issue Type: Improvement > Components: Index > Reporter: Otis Gospodnetic > Assignee: Michael Busch > Priority: Minor > Fix For: 2.3 > > Attachments: IndexReaderUtils.java, lucene-743-take2.patch, > lucene-743.patch, lucene-743.patch, lucene-743.patch, MyMultiReader.java, > MySegmentReader.java, varient-no-isCloneSupported.BROKEN.patch > > > This is Robert Engels' implementation of IndexReader.reopen() functionality, > as a set of 3 new classes (this was easier for him to implement, but should > probably be folded into the core, if this looks good). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]