accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1593) Looking up instanceName in ZK doesn't use consistent encoding
Date Mon, 02 Sep 2013 17:19:51 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756182#comment-13756182
] 

Mike Drob commented on ACCUMULO-1593:
-------------------------------------

Yea, the string v long decision should be a separate discussion. The patch looks good, but
there is one other scenario that I thought of.

Could this break compatibility when upgrading from 1.5? I'm reasonably confident that a UUID
serializes the same between ASCII, UTF-8, and CP1252. However, I have no idea what people
use for their instance names and maybe that deserves an extra check. Probably could be a separate
JIRA. [~ctubbsii], what do you think?
                
> Looking up instanceName in ZK doesn't use consistent encoding
> -------------------------------------------------------------
>
>                 Key: ACCUMULO-1593
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1593
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Christopher Tubbs
>            Assignee: Ted Yu
>              Labels: newbie
>             Fix For: 1.6.0
>
>         Attachments: accumulo-1593-v1.txt, accumulo-1593-v2.txt
>
>
> We need to be more careful about encoding and decoding instance names and IDs in zookeeper.
They should use UTF-8 explicitly, right now, they use the JVM default, which can differ between
JVM runs (even between Initialize and start-all).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message