lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-2034) javabin should use UTF-8, not modified UTF-8
Date Thu, 19 Aug 2010 20:24:16 GMT

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

Yonik Seeley commented on SOLR-2034:
------------------------------------

Seems OK.  I think modified UTF-8 was originally used so that the string chars could be directly
written to the output stream instead of to a temp buffer.  But copying to a temp buffer first
shouldn't have that much overhead.

JavaBinCodec.VERSION should be bumped.
It is serialized and verified when decoding, and currently an exception is thrown if it does
not match the current version.

> 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
>         Attachments: 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


Mime
View raw message