[ 
https://issues.apache.org/jira/browse/SOLR-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928129#action_12928129
 ] 

Shawn Heisey commented on SOLR-2204:
------------------------------------

I was planning to add 4.0 to the list of affected versions, but realized that 
it should be fine replicating with 3.1 as long as they both have the same 
javabin format.  Plus, there is already an existing barrier to upgrading 
directly from 1.4 to 4.0 - the index format itself.

I don't see a problem with making changes that are incompatible between 4.0 (or 
3.2) and 1.4, since they are so far apart.   IMHO the scenario I'm in, with the 
last release of one major version and the first release (well, current 
snapshot) of the next major version, it should be possible.


> 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: Next
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


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

Reply via email to