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

Jason Gerlowski commented on SOLR-17024:
----------------------------------------

Not quite sure what backcompat requires of us here in terms of the next 9.x 
release.  Are we safe to remove this in 9.5, since it's been deprecated for 
several major releases?  Or does the fact that we never followed through in 
removing it for 9.0 tie us to keeping it around until 10.0?

> Remove support for deprecated "collection-default clusterprop syntax
> --------------------------------------------------------------------
>
>                 Key: SOLR-17024
>                 URL: https://issues.apache.org/jira/browse/SOLR-17024
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 9.5
>            Reporter: Jason Gerlowski
>            Assignee: Jason Gerlowski
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> SOLR-12827 changed the structure that Solr uses to store collection-default 
> clusterprops all the way back in 8.0.
> Prior to 8.0, collection-default clusterprops were specified using a 
> {{collectionDefaults}} key, as in:
> {code}
> {
>   "collectionDefaults" : {
>       "numShards": 2,
>       "numNrtReplicas": 2,
>   }
> }
> {code}
> Starting with 8.0, this was changed to a format that relies on additional 
> nesting:
> {code}
> {
>   "defaults" : {
>     "collection": {
>       "numShards": 2,
>       "numNrtReplicas": 2,
>     }
>   }
> }
> {code}
>  
> SOLR-12827 deprecated the old format and removed all documentation 
> referencing it.  The code itself though still has a few vestiges of this old 
> format.  This ticket aims to remove these last traces of the old format.



--
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