You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/07/25 23:49:20 UTC
[jira] [Updated] (PHOENIX-3118) Increase default value of
hbase.client.scanner.max.result.size
[ https://issues.apache.org/jira/browse/PHOENIX-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-3118:
----------------------------------
Description: See parent JIRA for a discussion on how to handle partial scan results. An easy workaround would be to increase the {{hbase.client.scanner.max.result.size}} above the default 2MB limit. In combination with this, we could detect in BaseScannerRegionObserver.nextRaw() if partial results are being returned and throw an exception. Silently ignoring this is bad because it can lead to incorrect query results as demonstrated by the parent JIRA. (was: See parent JIRA for a discussion on how to handle partial scan results. An easy workaround would be to increase the {{hbase.client.scanner.max.result.size}} above the default 2GB limit. In combination with this, we could detect in BaseScannerRegionObserver.nextRaw() if partial results are being returned and throw an exception. Silently ignoring this is bad because it can lead to incorrect query results as demonstrated by the parent JIRA.)
> Increase default value of hbase.client.scanner.max.result.size
> --------------------------------------------------------------
>
> Key: PHOENIX-3118
> URL: https://issues.apache.org/jira/browse/PHOENIX-3118
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Fix For: 4.8.1
>
>
> See parent JIRA for a discussion on how to handle partial scan results. An easy workaround would be to increase the {{hbase.client.scanner.max.result.size}} above the default 2MB limit. In combination with this, we could detect in BaseScannerRegionObserver.nextRaw() if partial results are being returned and throw an exception. Silently ignoring this is bad because it can lead to incorrect query results as demonstrated by the parent JIRA.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)