[
https://issues.apache.org/jira/browse/HBASE-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370140#comment-14370140
]
Jonathan Lawlor commented on HBASE-13292:
-----------------------------------------
With this rolling back, we will also need to revert the change made to the
default value of caching (hbase.client.scanner.caching) made in HBASE-11544. In
HBASE-11544 caching default was changed to Integer.MAX_VALUE because the
default value of the max result size had been lowered to 2mb. We may want to
combine the reverts into one patch because rolling back the maxResultSize only
will produce the default config of maxResultSize=Long.Max_Value and
caching=Integer.Max_Value (if they should be dealt with in separate patches let
me know and I'll file one for caching). Should we revert to the previous
defaults of maxResultSize=Long.Max_Value and caching=100?
> Undo parent: setting hbase.client.scanner.max.result.size is considered
> harmful
> -------------------------------------------------------------------------------
>
> Key: HBASE-13292
> URL: https://issues.apache.org/jira/browse/HBASE-13292
> Project: HBase
> Issue Type: Sub-task
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Blocker
> Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.12
>
>
> Defaulting hbase.client.scanner.max.result.size to 2mb will have to be undone
> from all branches.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
