[
https://issues.apache.org/jira/browse/LUCENE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696550#action_12696550
]
Michael McCandless commented on LUCENE-1584:
--------------------------------------------
bq. This is required in one form or another for any kinds of segment-aware
caches.
The problem is you need more information than simply "these segments got
merged" to actually do something interesting with your caches.
EG you'd need to know which deleted docs got zapped, right?
bq. We're currently using our own field cache (I doubt we'll ever switch back
to lucene's native, fixed one or not)
Can you explain what's missing in Lucene's FieldCache? (Since we are going to
build a new one for LUCENE-831 it'd be great to address all known
limitations...).
> Callback for intercepting merging segments in IndexWriter
> ---------------------------------------------------------
>
> Key: LUCENE-1584
> URL: https://issues.apache.org/jira/browse/LUCENE-1584
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: 2.4.1
> Reporter: Jason Rutherglen
> Priority: Minor
> Fix For: 2.9
>
> Attachments: LUCENE-1584.patch
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> For things like merging field caches or bitsets, it's useful to
> know which segments were merged to create a new segment.
--
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
