[
https://issues.apache.org/jira/browse/HBASE-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437439#comment-13437439
]
Hadoop QA commented on HBASE-5251:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12541509/patch8.diff
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 16 new or modified tests.
+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The applied patch generated 5 javac compiler warnings (more than
the trunk's current 4 warnings).
-1 findbugs. The patch appears to introduce 8 new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2615//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2615//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2615//console
This message is automatically generated.
> Some commands return "0 rows" when > 0 rows were processed successfully
> -----------------------------------------------------------------------
>
> Key: HBASE-5251
> URL: https://issues.apache.org/jira/browse/HBASE-5251
> Project: HBase
> Issue Type: Bug
> Components: shell
> Affects Versions: 0.90.5
> Reporter: David S. Wang
> Assignee: Sameer Vaishampayan
> Priority: Minor
> Labels: noob
> Attachments: patch7.diff, patch8.diff
>
>
> From the hbase shell, I see this:
> hbase(main):049:0> scan 't1'
> ROW COLUMN+CELL
>
> r1 column=f1:c1, timestamp=1327104295560, value=value
>
> r1 column=f1:c2, timestamp=1327104330625, value=value
>
> 1 row(s) in 0.0300 seconds
> hbase(main):050:0> deleteall 't1', 'r1'
> 0 row(s) in 0.0080 seconds <====== I expected this to read
> "2 row(s)"
> hbase(main):051:0> scan 't1'
> ROW COLUMN+CELL
>
> 0 row(s) in 0.0090 seconds
> I expected the deleteall command to return "1 row(s)" instead of 0, because 1
> row was deleted. Similar behavior for delete and some other commands. Some
> commands such as "put" work fine.
> Looking at the ruby shell code, it seems that formatter.footer() is called
> even for commands that will not actually increment the number of rows
> reported, such as deletes. Perhaps there should be another similar function
> to formatter.footer(), but that will not print out @row_count.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
