stack created HBASE-16987:
-----------------------------
Summary: Update javadoc, refguide, and unit tests so ""...setting
[scan] cache is ... old style..."; instead limit by size and time.
Key: HBASE-16987
URL: https://issues.apache.org/jira/browse/HBASE-16987
Project: HBase
Issue Type: Sub-task
Components: scan
Reporter: stack
As [~yangzhe1991] says up in the parent issue, ""...Setting cache is an old
style to limit size and time...". Lets make this indeed the case by updating
javadoc, unit tests, and refguide in 1.3 (?) going forward.
Setting how many rows to get at a time when scanning was always
less-than-satisfactory, unpredictable as the data a row could contain. The hard
work done to get us up on a size/time basis should be underlined and
evangelized as the new norm. Thats what this issue is about (see parent issue
for the kinds of problems we run into when it caching is the awkward row-count
basis).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
