[ https://issues.apache.org/jira/browse/HBASE-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499079#comment-14499079 ]
Hadoop QA commented on HBASE-13090: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12725996/HBASE-13090-v7.patch against master branch at commit e08ef99e3042767eaf2d11adae783674acfdddeb. ATTACHMENT ID: 12725996 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 16 new or modified tests. {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions (2.4.1 2.5.2 2.6.0) {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 protoc{color}. The applied patch does not increase the total number of protoc compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:red}-1 checkstyle{color}. The applied patch generated 1911 checkstyle errors (more than the master's current 1910 errors). {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 lineLengths{color}. The patch introduces the following lines longer than 100: + new java.lang.String[] { "Region", "Scan", "ScannerId", "NumberOfRows", "CloseScanner", "NextCallSeq", "ClientHandlesPartials", "ClientHandlesHeartbeats", }); + new java.lang.String[] { "CellsPerResult", "ScannerId", "MoreResults", "Ttl", "Results", "Stale", "PartialFlagPerResult", "MoreResultsInRegion", "HeartbeatMessage", }); + public synchronized boolean next(List<Cell> outResults, ScannerContext scannerContext) throws IOException { {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/13727//testReport/ Release Findbugs (version 2.0.3) warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/13727//artifact/patchprocess/newFindbugsWarnings.html Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/13727//artifact/patchprocess/checkstyle-aggregate.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/13727//console This message is automatically generated. > Progress heartbeats for long running scanners > --------------------------------------------- > > Key: HBASE-13090 > URL: https://issues.apache.org/jira/browse/HBASE-13090 > Project: HBase > Issue Type: New Feature > Reporter: Andrew Purtell > Assignee: Jonathan Lawlor > Attachments: HBASE-13090-v1.patch, HBASE-13090-v2.patch, > HBASE-13090-v3.patch, HBASE-13090-v3.patch, HBASE-13090-v4.patch, > HBASE-13090-v6.patch, HBASE-13090-v7.patch > > > It can be necessary to set very long timeouts for clients that issue scans > over large regions when all data in the region might be filtered out > depending on scan criteria. This is a usability concern because it can be > hard to identify what worst case timeout to use until scans are > occasionally/intermittently failing in production, depending on variable scan > criteria. It would be better if the client-server scan protocol can send back > periodic progress heartbeats to clients as long as server scanners are alive > and making progress. > This is related but orthogonal to streaming scan (HBASE-13071). -- This message was sent by Atlassian JIRA (v6.3.4#6332)