[
https://issues.apache.org/jira/browse/LUCENE-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984742#action_12984742
]
Michael McCandless commented on LUCENE-2558:
--------------------------------------------
bq. In regards to the deltas, when they're in RAM (ie, for norm and DF
updates), I'm guessing we'd need to place the updates into a hash map (that
hopefully uses primitives instead of objects to save RAM)? We could instantiate
a new array when the map reached a certain size?
Actually I think all lookups for a del doc should still be against the BV.
The "generations"/replay log would only be used to properly do the recycling of
an old BV (ie, so you know which parts of the log to "replay" against this BV).
And, for saving the new deletes in the directory (though this is not really
important for the RT case).
> Use sequence ids for deleted docs
> ---------------------------------
>
> Key: LUCENE-2558
> URL: https://issues.apache.org/jira/browse/LUCENE-2558
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Affects Versions: Realtime Branch
> Reporter: Jason Rutherglen
> Priority: Minor
> Fix For: Realtime Branch
>
>
> Utilizing the sequence ids created via the update document
> methods, we will enable IndexReader deleted docs over a sequence
> id array.
> One of the decisions is what primitive type to use. We can start
> off with an int[], then possibly move to a short[] (for lower
> memory consumption) that wraps around.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
