On 5/10/2013 10:18 PM, Shawn Heisey wrote:
On 5/10/2013 7:42 PM, Michael Sokolov wrote:
My question is: is this intentional? It's unfortunate that we don't
seem to be able to update the client and have it continue to work with
(ie send updates to) the old servers. We have a centralized client
library that we share across a large number of different installations,
and getting all the servers upgraded is going to take some time. It
would be really nice if we could decouple the upgrade efforts.
I have a SolrJ 4.2.1 client that keeps both copies of my index up to
date. A single program runs and updates both, it's not multiple copies.
One of those copies is running 3.5.0 and the other has been upgraded to
4.2.1. I haven't had any trouble with javabin.
OK - I couldn't believe this was a universal problem that had gone
unnoticed for a year or more. Must be something weird in our setup.
I'm still trying to figure that out. I had gone so far as intercepting
the /update requests (in HttpClient) and rewriting them to
/update/javabin. But when I do that I am getting a different error when
inserting documents (Unknown type 16 at
org.apache.solr.common.util.JavaBinCodec.readVal(JavaBinCodec.java:216))
which seems like it might be a clue.
I'll post back when I know more in case someone else ends up in this hole.
-Mike
