[
https://issues.apache.org/jira/browse/HBASE-10163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849791#comment-13849791
]
Enis Soztutar commented on HBASE-10163:
---------------------------------------
bq.Maybe add explicit timestamps?
Unfortunately, Thrift API has different methods for doing puts with and without
timestamps:
{code}
client.mutateRow(ByteBuffer.wrap(t), ByteBuffer.wrap(row), mutations,
dummyAttributes);
..
client.mutateRowTs(ByteBuffer.wrap(t), ByteBuffer.wrap(row), mutations, 1,
dummyAttributes);
{code}
In DemoClient, we are using both of these to test them separately.
> Example Thrift DemoClient is flaky
> ----------------------------------
>
> Key: HBASE-10163
> URL: https://issues.apache.org/jira/browse/HBASE-10163
> Project: HBase
> Issue Type: Bug
> Components: Thrift
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Priority: Trivial
> Fix For: 0.98.0, 0.96.2, 0.99.0
>
> Attachments: hbase-10163_v1.patch
>
>
> DemoClient for thrift under hbase-examples is failing sometimes because of
> earlier delete eclipses future puts with same timestamp.
> {code}
> row: 00006, cols: unused: => DELETE_ME;
> row: 00006, cols: entry:num => -1;
> row: 00006, cols: entry:num => 6; entry:sqr => 36;
> row: 00006, cols: entry:num => 6; entry:sqr => 36;
> row: 00006, values: 6; -1;
> row: 00005, cols: unused: => DELETE_ME;
> row: 00005, values:
> FATAL: wrong # of versions
> {code}
> Similar to the one we have, we can add another small sleep between delete and
> subsequent put.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
