[
https://issues.apache.org/jira/browse/SOLR-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084713#comment-13084713
]
Mike Sokolov commented on SOLR-2204:
------------------------------------
Would it make sense to restore the old (CESU, I think?) UTF-8 encoding as a
fallback for the javabin protocol that would be used after some protocol
version negotiation indicated that either client or server only supports
javabin version 1?
If we don't, this seems like a headache for upgrading; you'd really like to be
able to upgrade different pieces of a large installation independently.
I was looking at this and have a half-baked untried patch which handles the
client side of the negotiation, but before spending more time on it I was
hoping to get some opinions.
> Cross-version replication broken by new javabin format
> ------------------------------------------------------
>
> Key: SOLR-2204
> URL: https://issues.apache.org/jira/browse/SOLR-2204
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
> Affects Versions: 3.1
> Environment: Linux idxst0-a 2.6.18-194.3.1.el5.centos.plusxen #1 SMP
> Wed May 19 09:59:34 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.6.0_20"
> Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
> Reporter: Shawn Heisey
> Fix For: 3.4, 4.0
>
>
> Slave server is branch_3x, revision 1027974. Master server is 1.4.1.
> Replication fails because of the new javabin format.
> SEVERE: Master at: http://HOST:8983/solr/live/replication is not available.
> Index fetch failed. Exception: Invalid version or the data in not in
> 'javabin' format
> Switching Solr's internally generated requests to XML, or adding support for
> both javabin versions would get rid of this problem. I do not know how to do
> either of these things.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
