[
https://issues.apache.org/jira/browse/SOLR-14165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-14165:
------------------------------
Fix Version/s: 8.4.1
> SolrResponse serialVersionUID has changed
> -----------------------------------------
>
> Key: SOLR-14165
> URL: https://issues.apache.org/jira/browse/SOLR-14165
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Andy Webb
> Priority: Major
> Fix For: 8.4.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SOLR-13821 changed the signature of
> {{org.apache.solr.client.solrj.SolrResponse}}, making serialisations of the
> class incompatible between versions.
> Original text from SOLR-13821:
> {quote}
> hi,
> We've been experimenting with doing a rolling in-place upgrade from Solr
> 8.3.1 to 8.4.0 on a non-production system, but have found that we get this
> exception for some operations, including when requesting
> /solr/admin/collections?action=overseerstatus on a node whose version is
> inconsistent with the overseer:
> java.io.InvalidClassException: org.apache.solr.client.solrj.SolrResponse;
> local class incompatible: stream classdesc serialVersionUID =
> -7931100103360242645, local class serialVersionUID = 2239939671435624715
> As far as I can see, this is due to the change to the SolrResponse class's
> signature in commit e3bd5a7. My experimentation has shown that if the
> serialVersionUID of that class is set explicitly to its previous value the
> exception no longer occurs.
> I'm not sure if this is a necessary or good fix, but I wanted to share this
> issue with you in case it's something that you think needs resolving.
> thanks,
> Andy
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
