You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Mike Drob (Jira)" <ji...@apache.org> on 2020/06/23 16:37:00 UTC

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

    [ https://issues.apache.org/jira/browse/SOLR-14582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143093#comment-17143093 ] 

Mike Drob commented on SOLR-14582:
----------------------------------

Should we have a warning if somebody tries to use this with the default MergePolicy to indicate that there will be no effect?

> Expose IWC.setMaxCommitMergeWaitSeconds 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
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Tomas Eduardo Fernandez Lobbe
>            Priority: Trivial
>
> 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