[
https://issues.apache.org/jira/browse/HBASE-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673433#comment-13673433
]
Jean-Marc Spaggiari commented on HBASE-8678:
--------------------------------------------
sorry, I went totally wrong way! Forget my 2 previous posts please.
Your example is normal behavior.
If you put a delete at timestamp=1, everything older than that is deleted. The
first cell you sent to HBase got the current time as the timestamp.
Can you please confirm what was your expectation?
> Wrongly delete cells in some case which can not be deleted
> ----------------------------------------------------------
>
> Key: HBASE-8678
> URL: https://issues.apache.org/jira/browse/HBASE-8678
> Project: HBase
> Issue Type: Bug
> Components: REST
> Affects Versions: 0.94.5, 0.95.0
> Environment: CentOS 5.5/hadoop0.20.2/hbase0.94.5/zookeeper3.4.3
> Reporter: Eric Huang
>
> First, I put a cell using put interface, but I don't specify timestamp. Then
> I delete the the same row, specify a timestamp of 1L. Unfortunately, the
> former cell is
> deleted. We should know this cell can not be deleted in this case. (Using
> original Client API)
> Code like this;
> public static void main(String[] args) throws Exception {
> Cluster cluster = new Cluster();
> cluster.add("10.28.171.38", 8080);
> Client client = new Client(cluster);
> RemoteHTable table = new RemoteHTable(client, "demotime");
>
> Put put = new Put(Bytes.toBytes("row21"));
> put.add("info".getBytes(), "name".getBytes(), "huanggang".getBytes());
> table.put(put);
>
> Delete delete = new Delete(Bytes.toBytes("row21"));
> delete.setTimestamp(1L);
> table.delete(delete);
> }
--
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
