[
https://issues.apache.org/jira/browse/HBASE-13799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565061#comment-14565061
]
stack commented on HBASE-13799:
-------------------------------
bq. why the setCaching()/setMaxResultSize() part was removed?
This stuff should not be front and center as it used to be. It will only
confuse now that scanner takes care of this under the covers for you (Scanner
is now 'size-based' where before it was 'row-based'...) I considered
'explaining' the new regime in the class comment but thought it would only
confuse more than it helped (We should do HBASE-13441 sooner rather than later
-- especially given review of the rest of Scan javadoc, it all needs revamp).
> javadoc how Scan gets polluted when used; if you set attributes or ask for
> scan metrics
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-13799
> URL: https://issues.apache.org/jira/browse/HBASE-13799
> Project: HBase
> Issue Type: Task
> Components: documentation
> Reporter: stack
> Assignee: stack
> Priority: Minor
> Attachments: 13799.txt
>
>
> Matteo is noticing that Get and Scan get altered when used. Doc it for Scans
> (Matteo is 'fixing' it for Get).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
