You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2010/10/28 00:04:26 UTC
[jira] Commented: (SOLR-2034) javabin should use UTF-8, not
modified UTF-8
[ https://issues.apache.org/jira/browse/SOLR-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925576#action_12925576 ]
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: https://issues.apache.org/jira/browse/SOLR-2034
> 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 (http://www.unicode.org/reports/tr26/)
--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org