[
https://issues.apache.org/jira/browse/LUCENE-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875027#action_12875027
]
Michael McCandless commented on LUCENE-2485:
--------------------------------------------
In addition to the "more context" that Yonik proposed (which I like), we could
also pass to the warmer whether the segment was created by flush or by merge or
by addIndexes.
This way the app could have a single place for all warming, but if necessary
can pick & choose how it warms the difference cases separately, since warming
after a merge is done in the background (won't block an NRT reopen).
I'd really like to first factor the ReaderPool out of IW though...
> 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]
