[jira] [Created] (TEPHRA-289) Update HBase 2.0 dependency to the released version

2018-05-03 Thread Poorna Chandra (JIRA)
Poorna Chandra created TEPHRA-289:
-

 Summary: Update HBase 2.0 dependency to the released version
 Key: TEPHRA-289
 URL: https://issues.apache.org/jira/browse/TEPHRA-289
 Project: Tephra
  Issue Type: Improvement
Reporter: Poorna Chandra
Assignee: Poorna Chandra
 Fix For: 0.14.0-incubating


HBase 2.0 was released on Apr 30 2018. Update the HBase 2.0 dependency from 
{{2.0.0-beta-1}} to {{2.0.0}} once the 2.0 jars are available on the Maven 
Central repository. 



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


[jira] [Commented] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly

2018-05-03 Thread Poorna Chandra (JIRA)

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

Poorna Chandra commented on TEPHRA-287:
---

Hi [~jamestaylor], since the changes are a bit large, can you open a PR [1] in 
the Tephra Github repository? It would make the review easier.

[1] - [https://tephra.incubator.apache.org/HowToContribute.html]

> 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, 
> TEPHRA-287_v3.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)