You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2009/10/29 17:52:59 UTC

[jira] Commented: (HBASE-1941) Put's copy feature has a bug.

    [ https://issues.apache.org/jira/browse/HBASE-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771476#action_12771476 ] 

Hyunsik Choi commented on HBASE-1941:
-------------------------------------

Consequently, this bug affects TableOutputFormat.class.

> Put's copy feature has a bug.
> -----------------------------
>
>                 Key: HBASE-1941
>                 URL: https://issues.apache.org/jira/browse/HBASE-1941
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.20.1
>            Reporter: Hyunsik Choi
>
> Put's copy feature has a bug. The copy does not consider the timestamp value.
> In the following example, a put and its copied put prints out different timestamps.
> {quote}
> Put put = new Put("abc".getBytes());
> put.setTimeStamp(1);
> System.out.println(put.getTimeStamp());
> Put put2 = new Put(put);
> System.out.println(put2.getTimeStamp());
> ---------------------------
> Above source code results in as follows:
> 1
> 9223372036854775807
> {quote}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.