Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 206D8102FF for ; Tue, 4 Jun 2013 19:39:23 +0000 (UTC) Received: (qmail 80775 invoked by uid 500); 4 Jun 2013 19:39:22 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 80738 invoked by uid 500); 4 Jun 2013 19:39:22 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 80729 invoked by uid 99); 4 Jun 2013 19:39:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Jun 2013 19:39:22 +0000 Date: Tue, 4 Jun 2013 19:39:22 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8678) Wrongly delete cells in some case which can not be deleted MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675148#comment-13675148 ] Hadoop QA commented on HBASE-8678: ---------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12586140/HBASE-8678-v1-trunk.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop 1.0 profile. {color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 lineLengths{color}. The patch does not introduce lines longer than 100 {color:green}+1 site{color}. The mvn site goal succeeds with this patch. {color:green}+1 core tests{color}. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/5930//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5930//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5930//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5930//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5930//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5930//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5930//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5930//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/5930//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/5930//console This message is automatically generated. > 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 > Assignee: Jean-Marc Spaggiari > Attachments: HBASE-8678-v0-trunk.patch, HBASE-8678-v1-trunk.patch > > > 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