[jira] [Resolved] (SOLR-16255) Introduce DirectUpdateHandler2#shouldCommit

["Bruno Roustant (Jira)" <ji...@apache.org>]

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

Bruno Roustant resolved SOLR-16255.
-----------------------------------
    Fix Version/s: 9.1
       Resolution: Fixed

> Introduce DirectUpdateHandler2#shouldCommit
> -------------------------------------------
>
>                 Key: SOLR-16255
>                 URL: https://issues.apache.org/jira/browse/SOLR-16255
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Bruno Roustant
>            Priority: Major
>             Fix For: 9.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently DirectUpdateHandler2 checks IndexWriter.hasUncommittedChanges() before effectively calling IndexWriter.commit().
> It is also possible for the user to provide custom commit metadata in the CommitUpdateCommand.commitData field.
> The proposed change is to move the check to IndexWriter.hasUncommittedChanges() in a new protected method DirectUpdateHandler2.shouldCommit(), which would also check (logical or) if the CommitUpdateCommand contains user defined commit metadata. It becomes possible to commit without change, but with user defined commit metadata.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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