tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Poorna Chandra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
Date Tue, 24 Apr 2018 18:29:00 GMT

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

Poorna Chandra commented on TEPHRA-287:
---------------------------------------

The config is a good idea James. This way we could upgrade the transaction manager first,
and then allow the clients to be upgraded later. During the time clients are being upgraded,
the transaction manager will accept change sets in both old and new format. Once all the clients
are upgraded, we can flip the flag, and the transaction manager will start rejecting the change
sets in the old format.

> ActionChange.getChangeKey() not implemented correctly
> -----------------------------------------------------
>
>                 Key: TEPHRA-287
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-287
>             Project: Tephra
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>            Priority: Major
>             Fix For: 0.14.0-incubating
>
>         Attachments: TEPHRA-287_v1.patch, TEPHRA-287_v2.patch
>
>
> The ActionChange.getChangeKey() simply concatenates together the row key, family, and
qualifier which could lead to incorrect conflicting keys. For example (rowKey='a', family='bc')
would conflict with (rowKey='ab', family='c'). A simple fix would be to prefix each part with
the byte length of each part.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message