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

ASF subversion and git services commented on SOLR-17712:
--------------------------------------------------------

Commit a4377386021c683a94aff80674b3ff212e45edf5 in solr's branch 
refs/heads/branch_10x from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=a4377386021 ]

SOLR-17712: Deprecating waitForFinalState parameter (#3756)

* SOLR-17712: Deprecating waitForFinalState parameter
  in any SolrCloud command that accepts it.

It remains defaulted to false in 9, but will become true and likely removed.

> SolrCloud: remove CommonAdminParams.waitForFinalState; default to TRUE
> ----------------------------------------------------------------------
>
>                 Key: SOLR-17712
>                 URL: https://issues.apache.org/jira/browse/SOLR-17712
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>            Reporter: David Smiley
>            Priority: Major
>              Labels: newdev, pull-request-available
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> Collection creation has an optional parameter 
> [waitForFinalState|https://solr.apache.org/guide/solr/latest/deployment-guide/collection-management.html#create]
>  :
> {quote}If {{{}true{}}}, the request will complete only when all affected 
> replicas become active. The default is {{{}false{}}}, which means that the 
> API will return the status of the single action, which may be before the new 
> replica is online and active.{quote}
> Wouldn’t a caller of a command (any command to anything; whatever) generally 
> expect that the command has completed when a command returns?  I question the 
> default choice of this parameter.  I believe it pre-dated the more general 
> “async” support of collection commands.
>  
> Proposal: remove it.  Internal logic should behave as if it's "true".
>  
> Come to think of it, I see this in quite a number of other commands involving 
> replica creations too.
> First baby step (individual PR) might simply be to change the default and 
> wait some weeks through tests.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to