[ https://issues.apache.org/jira/browse/HBASE-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500331#comment-14500331 ]
Nick Dimiduk commented on HBASE-13090: -------------------------------------- bq. I wanted to put this in hbase 1.1 because it so sweet but [~jonathan.lawlor] won't let me... says too much change too close to release.... it might be a bit 'risky'. Ahem. That's a shame; this seems very important for Phoenix users who are pushing the line on OLAP-kinds of queries. What can we do to raise your confidence in the patch for branch-1.1? IT tests? CM? > 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 > Fix For: 2.0.0, 1.2.0 > > 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)