[
https://issues.apache.org/jira/browse/SOLR-9511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15694774#comment-15694774
]
Noble Paul commented on SOLR-9511:
----------------------------------
Do we have the individual versions API used anywhere?
We keep old APIs available for a few extra releases. The reason is when you do
a rolling restart after upgrading your solr version, some nodes will expect the
old API to be available while the other node may not have it. So, what we need
to do is to ensure that
1) No code uses the old APi for the last 2 or 3 releases
2) ensure that the "upgrading from Solrx.x" in CHNAGES.txt has the relevant
information
> Retire using individual versions to request updates during PeerSync
> -------------------------------------------------------------------
>
> Key: SOLR-9511
> URL: https://issues.apache.org/jira/browse/SOLR-9511
> Project: Solr
> Issue Type: Wish
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: master (7.0)
> Reporter: Pushkar Raste
> Priority: Minor
> Fix For: master (7.0)
>
> Attachments: SOLR-9511.patch
>
>
> We started using version ranges to request updates during PeerSync in
> [SOLR-9207| https://issues.apache.org/jira/browse/SOLR-9207]. Using version
> ranges was also made default.
> There is no need to have code that uses individual versions start Solr 7.
> Decommission (remove unnecessary code)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
