[
https://issues.apache.org/jira/browse/PHOENIX-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011460#comment-17011460
]
Lars Hofhansl commented on PHOENIX-4266:
----------------------------------------
We can either set the default caching to Integer.MAX_VALUE (that's what HBase
does now by default), or simply remove the default from Phoenix completely. In
any case, it is time to do this after over 2 years.
> Avoid scanner caching in Phoenix
> --------------------------------
>
> Key: PHOENIX-4266
> URL: https://issues.apache.org/jira/browse/PHOENIX-4266
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Priority: Major
> Fix For: 5.1.0, 4.16.0
>
>
> Phoenix tries to set caching on all scans. On HBase versions before 0.98 that
> made sense, now it is the wrong thing to do.
> HBase will by default do size based chunking. Setting scanner caching
> prevents HBase doing this work.
> We should avoid scanner everywhere, and only use in cases where we know the
> number of rows to be returned (and that number is small).
> [~sergey.soldatov], [~jamestaylor]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
