[
https://issues.apache.org/jira/browse/LUCENE-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711139#action_12711139
]
Earwin Burrfoot commented on LUCENE-1645:
-----------------------------------------
bq. Right; I think we should simply clone shared subreaders on reopen.
IFF the subreader being cloned is not readonly!
bq. I think it's too soon to do this.
Hey, let's reverse readonly/writeable reader inheritance?
WriteableSegmentReader extends SegmentReader.
SegmentReader is readonly by behaviour and in code - there are no syncs and
mutator methods throw UOE. WriteableSegmentReader adds a writeability layer
over SegmentReader and all the gory syncs.
bq. I think we do? Eg it enables you to clone a readOnly reader to a read/write
one in order to do deletes/setNorm.
Hey, open a new IR if you want to write. Cloning/reopening an IR while
simultaneously switching readonly flag is a feature that gives user zero new
functionality, absolutely nothing he can't accomplish using a new IR, but makes
reopening/cloning code more complex.
> Deleted documents are visible across reopened MSRs
> --------------------------------------------------
>
> Key: LUCENE-1645
> URL: https://issues.apache.org/jira/browse/LUCENE-1645
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 2.9
> Reporter: Earwin Burrfoot
> Fix For: 2.9
>
> Attachments: LUCENE-1645.patch
>
>
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
