[
https://issues.apache.org/jira/browse/SOLR-6732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter updated SOLR-6732:
---------------------------------
Attachment: SOLR-6732.patch
Here's an updated patch that should allow for hot, rolling upgrades - handling
the String state or JSON map correctly. I've added a unit test that checks for
back-compat support.
The other concern is a node running old code that expects a String state and
not the JSON map. I think that will not cause any issues since it will just
treat the map as a String; a recovering replica will just delete the value once
it's active.
However, before I commit this I'll do a rolling upgrade to ensure no issues
when going from 4.8.x to 4.10.3
> Back-compat break for LIR state in 4.10.2
> -----------------------------------------
>
> Key: SOLR-6732
> URL: https://issues.apache.org/jira/browse/SOLR-6732
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.10.2
> Reporter: Shalin Shekhar Mangar
> Assignee: Timothy Potter
> Priority: Blocker
> Fix For: 4.10.3
>
> Attachments: SOLR-6732.patch, SOLR-6732.patch
>
>
> We changed the LIR state to be kept as a map but it is not back-compatible.
> The problem is that we're checking for map or string after parsing JSON but
> if the key has "down" as a string then json parsing will fail.
> This was introduced in SOLR-6511. This error will prevent anyone from
> upgrading to 4.10.2
> http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201411.mbox/%3c54636ed2.8040...@cytainment.de%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
