[ 
https://issues.apache.org/jira/browse/SOLR-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Smiley updated SOLR-3999:
-------------------------------

    Fix Version/s:     (was: 4.7)
                   4.8

> No serialVersionUID in SolrInputDocument and SolrInputField
> -----------------------------------------------------------
>
>                 Key: SOLR-3999
>                 URL: https://issues.apache.org/jira/browse/SOLR-3999
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 3.6, 4.0
>            Reporter: yuanyun.cn
>             Fix For: 4.8
>
>
> In my solr server, one field is binarydoc which stores a SolrInputDocument; 
> it contains some essential fields. - We do this to improve the transfer 
> performance and some other desgin consideration, when copy the index of one 
> document to another solr server, we only need copy the binarydoc field.
> But when the client(3.6) and server(3.1) are not at same version, this would 
> fail with error:
> java.io.InvalidClassException: org.apache.solr.common.SolrInputDocument; 
> local class incompatible: stream classdesc serialVersionUID = 
> -933324331332362318, local class serialVersionUID = 
> 7513968456965125205L4675759
> The root cause if that SolrInputDocument doesn't provide a default 
> serialVersionUID, and different version has different serialVersionUID.
> When client is 4.0, server is 3.1, it report one more error:
> java.io.InvalidClassException: org.apache.solr.common.SolrInputField; local 
> class incompatible: stream classdesc serialVersionUID = -837387721983293523, 
> local class serialVersionUID = 6061428683263691882
> 6061428683263691882
> I temporarily fixed the error by adding serialVersionUID to client and server 
> code with same value.
> Please fix this :)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to