lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1329) Remove synchronization in SegmentReader.isDeleted
Date Fri, 08 Aug 2008 19:37:44 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621024#action_12621024
] 

Yonik Seeley commented on LUCENE-1329:
--------------------------------------

bq. I didn't do this one yet ... it makes me a bit nervous because it means that people who
just do IndexReader.open on an index with no deletions pay the RAM cost upfront of allocating
the BitVector.

Right, which is why I said it was for a "deleting-reader" (which presumes the existence of
read-only-readers).


> 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, 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message