[
https://issues.apache.org/jira/browse/SOLR-11860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker updated SOLR-11860:
-
Description:
Today the add collection command explicitly set's the collection state to
version 2 if not explicitly specified. The default behavior is still
stateFormat=1
Because of this we found bugs like SOLR-11586 .
Solr should change the default state format instead of individual APIs having
to explicitly set is . The patch provided by Tim Owen on SOLR-11832 would be
applicable here
> Change the default state format to 2
>
>
> Key: SOLR-11860
> URL: https://issues.apache.org/jira/browse/SOLR-11860
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Environment: Today the add collection command explicitly set's the
> collection state to version 2 if not explicitly specified. The default
> behavior is still stateFormat=1
>
> Because of this we found bugs like SOLR-11586 .
>
> Solr should change the default state format instead of individual APIs having
> to explicitly set is . The patch provided by Tim Owen on SOLR-11832 would be
> applicable here
>Reporter: Varun Thacker
>Priority: Major
>
> Today the add collection command explicitly set's the collection state to
> version 2 if not explicitly specified. The default behavior is still
> stateFormat=1
>
> Because of this we found bugs like SOLR-11586 .
>
> Solr should change the default state format instead of individual APIs having
> to explicitly set is . The patch provided by Tim Owen on SOLR-11832 would be
> applicable here
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org