[
https://issues.apache.org/jira/browse/LUCENE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696511#action_12696511
]
Earwin Burrfoot commented on LUCENE-1584:
-----------------------------------------
.bq I'd like to step back and understand the wider use case / context that's
driving this need (to know precisely when segments got merged)
This is required in one form or another for any kinds of segment-aware caches.
We're currently using our own field cache (I doubt we'll ever switch back to
lucene's native, fixed one or not) and filter cache. Both caches are warmed up
on reopen, asynchronously from search requests and both would warm up
considerably faster if we have data on how segments have changed.
> 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
