[
https://issues.apache.org/jira/browse/LUCENE-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874613#action_12874613
]
Yonik Seeley commented on LUCENE-2485:
--------------------------------------
I'm not sure how practical this is or not... but in general, more context would
enable a broader range of applications.
- Passing in the complete index (in addition to just the new segment) would
allow incremental updating of an index-wide data structure
- If the new segment was the result of a merge of existing segments, passing in
those existing segments could allow more efficient generation of cached items
from the cached items of the old segments.
> IndexWriter should also warm flushed segments
> ---------------------------------------------
>
> Key: LUCENE-2485
> URL: https://issues.apache.org/jira/browse/LUCENE-2485
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Reporter: Michael McCandless
> Fix For: 4.0
>
>
> Spinoff of LUCENE-2311.
> You can now set a mergedSegmentWarmer on IW, which warms only newly merged
> segments.
> But for consistency maybe we should change this to warm all new segments (ie,
> also flushed ones). We should rename it to something "setSegmentWarmer".
> Really, the reader pool should be pulled out of IndexWriter, be externally
> provided, and be responsible for doing warming of new segments.
--
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: [email protected]
For additional commands, e-mail: [email protected]
