[
https://issues.apache.org/jira/browse/LUCENE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695742#action_12695742
]
Michael McCandless commented on LUCENE-1584:
--------------------------------------------
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). EG if we fix
Lucene's field cache, and Lucene's near real-time search manages CSF's
efficiently in memory, does that address the use case behind this?
It's possible that we should simply make SegmentInfo(s) public, so that
MergePolicy/Scheduler can be fully created external to Lucene, and track all
specifics of why/when merges are happening. But those APIs have a high surface
area, and we do make changes over time.
> 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
