[
https://issues.apache.org/jira/browse/LUCENE-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611602#action_12611602
]
Yonik Seeley commented on LUCENE-1329:
--------------------------------------
Once we have a read-only IndexReader, if we still want the deleting-reader then
we could also weaken the semantics of deleteDocument such that applications
would need to synchronize themselves to guarantee visibility to another thread.
We could safely do this for a deleting-reader by pre-allocating the BitVector
objects, thus eliminating the possibility of a thread seeing a partially
constructed object.
> Remove synchronization in SegmentReader.isDeleted
> -------------------------------------------------
>
> Key: LUCENE-1329
> URL: https://issues.apache.org/jira/browse/LUCENE-1329
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: 2.3.1
> Reporter: Jason Rutherglen
> Priority: Trivial
> Attachments: lucene-1329.patch
>
>
> Removes SegmentReader.isDeleted synchronization by using a volatile
> deletedDocs variable on Java 1.5 platforms. On Java 1.4 platforms
> synchronization is limited to obtaining the deletedDocs reference.
--
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]
