You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Tomas Eduardo Fernandez Lobbe (Jira)" <ji...@apache.org> on 2020/08/07 18:02:00 UTC

[jira] [Resolved] (SOLR-14582) Expose IWC.setMaxCommitMergeWaitMillis as an expert feature in Solr's index config

     [ https://issues.apache.org/jira/browse/SOLR-14582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomas Eduardo Fernandez Lobbe resolved SOLR-14582.
--------------------------------------------------
    Fix Version/s: 8.7
                   master (9.0)
       Resolution: Fixed

> Expose IWC.setMaxCommitMergeWaitMillis as an expert feature in Solr's index config
> ----------------------------------------------------------------------------------
>
>                 Key: SOLR-14582
>                 URL: https://issues.apache.org/jira/browse/SOLR-14582
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Tomas Eduardo Fernandez Lobbe
>            Assignee: Tomas Eduardo Fernandez Lobbe
>            Priority: Trivial
>             Fix For: master (9.0), 8.7
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> LUCENE-8962 added the ability to merge segments synchronously on commit. This isn't done by default and the default {{MergePolicy}} won't do it, but custom merge policies can take advantage of this. Solr allows plugging in custom merge policies, so if someone wants to make use of this feature they could, however, they need to set {{IndexWriterConfig.maxCommitMergeWaitSeconds}} to something greater than 0.
> Since this is an expert feature, I plan to document it only in javadoc and not the ref guide.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org