SOLR-17712: Deprecating waitForFinalState parameter #3756
Conversation
in any SolrCloud command that accepts it. It remains defaulted to false in 9, but will become true and likely removed.
|
Should the |
|
I was only recently aware of |
# Conflicts: # solr/CHANGES.txt
|
We don't really have super strong patterns around how we label things. I think |
This reverts commit c894b6e.
|
It seems precommit is unhappy that we call the methods still with that forRemoval=true aspect. I don't want to deal with the matter so I reverted it, as we haven't been using that option. I'm more likely, going forward, to explicitly set it to false on something if I want to warn people not to use that might not be going away. I'll merge in a bit. |
* 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.
in any SolrCloud command that accepts it. It remains defaulted to false in 9, but will become true and likely removed. (cherry picked from commit 6eb910a)
* 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.
3 participants
in any SolrCloud command that accepts it.
It remains defaulted to false in 9, but will become true and likely removed.
https://issues.apache.org/jira/browse/SOLR-17712
This PR is very focused on only deprecations to also land on Solr 9. Crediting @abumarjikar . #3684 goes further with change of default