[
https://issues.apache.org/jira/browse/PHOENIX-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeongdae Kim updated PHOENIX-3486:
----------------------------------
Description: RoundRobinResultIterator uses "hbase.client.scanner.caching"
to fill caches in parallel for all scans, but by setting Scan.setCaching() in
PhoenixInputForrmat(phoenix-hive), RoundRobinResultIterator doesn't work
correctly, because if Scan have cache size by setCaching(), HBase set cache
size from Scan.getCaching() to fill cache, not "hbase.client.scanner.caching".
this causes scan performance degradation. (was: RoundRobinResultIterator uses
"hbase.client.scanner.caching" to fill caches in parallel for all scans, but
by setting Scan.setCaching() in PhoenixInputForrmat(phoenix-hive),
RoundRobinResultIterator doesn't work correctly, because if Scan have cache
size by setCaching(), HBase uses Scan.getCaching(), not
"hbase.client.scanner.caching". this causes scan performance degradation.)
> RoundRobinResultIterator doesn't work correctly because of setting Scan's
> cache size inappropriately in PhoenixInputForamt
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-3486
> URL: https://issues.apache.org/jira/browse/PHOENIX-3486
> Project: Phoenix
> Issue Type: Bug
> Reporter: Jeongdae Kim
> Assignee: Jeongdae Kim
> Labels: HivePhoenix
>
> RoundRobinResultIterator uses "hbase.client.scanner.caching" to fill caches
> in parallel for all scans, but by setting Scan.setCaching() in
> PhoenixInputForrmat(phoenix-hive), RoundRobinResultIterator doesn't work
> correctly, because if Scan have cache size by setCaching(), HBase set cache
> size from Scan.getCaching() to fill cache, not
> "hbase.client.scanner.caching". this causes scan performance degradation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
