phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3118) Increase default value of hbase.client.scanner.max.result.size
Date Thu, 08 Sep 2016 20:47:20 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474947#comment-15474947
] 

Lars Hofhansl commented on PHOENIX-3118:
----------------------------------------

Hmm... HBase doesn't automatically "trip" the partial result logic (at least not in 0.98).
Instead if a single row is > 2MB it will be returned in one PRC regardless of what the
HBase buffer size is. (will check 1.0+ as well).


> 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)

Mime
View raw message