[
https://issues.apache.org/jira/browse/HBASE-13215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364505#comment-14364505
]
He Liangliang commented on HBASE-13215:
---------------------------------------
The second approach.
In some of our application (actually most of online services), the number of
values in a row is bounded (like a RDBMS row), so this limit can be a soft
limit which can be exceeded without affect the time consumption much. Actually
breaking the row in the middle is quite undesirable for these type of
application (like the behavior of batch) which make the application logic
clumsy.
> A limit on the raw key values is needed for each next call of a scanner
> -----------------------------------------------------------------------
>
> Key: HBASE-13215
> URL: https://issues.apache.org/jira/browse/HBASE-13215
> Project: HBase
> Issue Type: Improvement
> Components: Scanners
> Reporter: He Liangliang
> Assignee: He Liangliang
>
> In the current scanner next, there are several limits: caching, batch and
> size. But there is no limit on raw data scanned, so the time consumed by a
> next call is unbounded. For example, many consecutive deleted or filtered out
> cells will leads to a socket timeout. This can make user code get stuck.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
