[
https://issues.apache.org/jira/browse/HBASE-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174593#comment-13174593
]
Hadoop QA commented on HBASE-4439:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12508335/4439-v2.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. 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.
-1 javadoc. The javadoc tool appears to have generated -152 warning
messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 77 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/577//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/577//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/577//console
This message is automatically generated.
> Move ClientScanner out of HTable
> --------------------------------
>
> Key: HBASE-4439
> URL: https://issues.apache.org/jira/browse/HBASE-4439
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.94.0
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Minor
> Fix For: 0.94.0
>
> Attachments: 4439-v1.txt, 4439-v2.txt, 4439.txt
>
>
> See HBASE-1935 for motivation.
> ClientScanner should be able to exist outside of HTable.
> While we're at it, we can also add an abstract client scanner to easy
> development of new client side scanners (such as parallel scanners, or per
> region scanners).
--
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
