lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <>
Subject [jira] Commented: (SOLR-2034) javabin should use UTF-8, not modified UTF-8
Date Wed, 27 Oct 2010 22:04:26 GMT


Shawn Heisey commented on SOLR-2034:

I started upgrading my slave shards today from 1.4.1 to 3.1 and ran into a bit of a showstopper:

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

What advice do you have?  I can't upgrade both master and slave at the same time - we have
to be able to fully test against the new version.  I would rather not do the testing with
completely static indexes, it would be better to have data being added and deleted normally.

> javabin should use UTF-8, not modified UTF-8
> --------------------------------------------
>                 Key: SOLR-2034
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>         Attachments: SOLR-2034.patch, SOLR-2034.patch, SOLR-2034.patch, SOLR-2034.patch
> for better interoperability, javabin should use standard UTF-8 instead of modified UTF-8

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:
For additional commands, e-mail:

View raw message