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 D333C10E84 for ; Sat, 20 Jul 2013 05:42:50 +0000 (UTC) Received: (qmail 35415 invoked by uid 500); 20 Jul 2013 05:42:50 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 35382 invoked by uid 500); 20 Jul 2013 05:42:49 -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 35368 invoked by uid 99); 20 Jul 2013 05:42:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Jul 2013 05:42:49 +0000 Date: Sat, 20 Jul 2013 05:42:49 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8780) a column Family can have VERSIONS less than zero 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-8780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714345#comment-13714345 ] Hadoop QA commented on HBASE-8780: ---------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12593320/HBASE-8780-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:red}-1 site{color}. The patch appears to cause mvn site goal to fail. {color:red}-1 core tests{color}. The patch failed these unit tests: org.apache.hadoop.hbase.regionserver.TestKeepDeletes org.apache.hadoop.hbase.regionserver.TestMinVersions org.apache.hadoop.hbase.TestHColumnDescriptor Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/6413//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6413//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6413//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6413//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6413//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6413//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6413//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6413//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6413//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/6413//console This message is automatically generated. > a column Family can have VERSIONS less than zero > ------------------------------------------------- > > Key: HBASE-8780 > URL: https://issues.apache.org/jira/browse/HBASE-8780 > Project: HBase > Issue Type: Bug > Components: Client > Affects Versions: 0.94.8 > Reporter: Demai Ni > Assignee: Demai Ni > Priority: Trivial > Attachments: HBASE-8780-0.94.8-v0.patch, HBASE-8780-test.txt, HBASE-8780-trunk.patch, HBASE-8780-trunk.patch > > > User can create/alter a columnfam and set its VERSION(aka maxVERSIONS) to a negative or zero value. Although there is a checking in HColumnDesciptor#construtor, hbase shell command will invoke the setter(setMaxVersions and setMinVersions) directly, hence by pass the checking. For example: > {code:title=set VERSIONS = -1} > hbase(main):016:0> create 't5_dn',{NAME=>'cf1',VERSIONS=>-1} > 0 row(s) in 1.0420 seconds > hbase(main):017:0> put 't5_dn','row1','cf1:q1','row1cf1_v1' > 0 row(s) in 0.0700 seconds > hbase(main):018:0> scan 't5_dn' > ROW COLUMN+CELL > 0 row(s) in 0.0090 seconds > hbase(main):019:0> describe 't5_dn' > DESCRIPTION ENABLED > 't5_dn', {NAME => 'cf1', REPLICATION_SCOPE => '0', true > KEEP_DELETED_CELLS => 'false', COMPRESSION => 'NONE > ', ENCODE_ON_DISK => 'true', BLOCKCACHE => 'true', > MIN_VERSIONS => '0', DATA_BLOCK_ENCODING => 'NONE', > IN_MEMORY => 'false', BLOOMFILTER => 'NONE', TTL = > > '2147483647', VERSIONS => '-1', BLOCKSIZE => '655 > 36'} > 1 row(s) in 0.0410 seconds > {code} > above example shows VERSIONS => '-1', and put/scan doesn't keep the data -- 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