[
https://issues.apache.org/jira/browse/LUCENE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609999#action_12609999
]
Michael McCandless commented on LUCENE-1314:
--------------------------------------------
bq. ...which led to some interesting discussion about what the semantics of
cloning an IndexReader should be (even though ultimately cloning wasn't used).
In fact that 2nd point you raised ("what happens when you clone an IndexReader
that has pending changes") makes me nervous here. I think I'd prefer that we
disallow that (throw an exception when this is attempted). Ie you can only
clone a reader that has no pending changes.
Also Jason you added set/getWriteLock: how come you couldn't just customize
LockFactory for that, instead? Eg if you want to turn off locking you can just
use NoLockFactory.
{quote}
Would like to be able to optionally have this line run in DirectoryIndexReader
in reopen. Does it need to be run on a clone?
SegmentInfos infos = new SegmentInfos();
infos.read(directory, segmentFileName);
{quote}
I agree that line should not run on clone().
> IndexReader.reopen(boolean force)
> ---------------------------------
>
> Key: LUCENE-1314
> URL: https://issues.apache.org/jira/browse/LUCENE-1314
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Index
> Affects Versions: 2.3.1
> Reporter: Jason Rutherglen
> Assignee: Michael McCandless
> Priority: Minor
> Attachments: lucene-1314.patch, lucene-1314.patch, lucene-1314.patch,
> lucene-1314.patch
>
>
> Based on discussion
> http://www.nabble.com/IndexReader.reopen-issue-td18070256.html. The problem
> is reopen returns the same reader if there are no changes, so if docs are
> deleted from the new reader, they are also reflected in the previous reader
> which is not always desired behavior.
--
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]
