lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-2485) IndexWriter should also warm flushed segments
Date Wed, 02 Jun 2010 15:23:54 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874611#action_12874611
] 

Yonik Seeley commented on LUCENE-2485:
--------------------------------------

bq. But for consistency maybe we should change this to warm all new segments

As long as warming a new segment doesn't block that new segment from being exposed via getReader()?

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message