You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "yunjiong zhao (JIRA)" <ji...@apache.org> on 2016/03/31 20:00:29 UTC
[jira] [Commented] (KYLIN-1545) should not setMaxResultSize on
hbase scan as it might cause incorrect answers
[ https://issues.apache.org/jira/browse/KYLIN-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220335#comment-15220335 ]
yunjiong zhao commented on KYLIN-1545:
--------------------------------------
Why do you think setMaxResultSize will cause problem?
According to hbase, it shouldn't cause incorrect answers:
{quote}
/**
* Maximum number of bytes returned when calling a scanner's next method.
* Note that when a single row is larger than this limit the row is still
* returned completely.
*
* The default value is 2MB.
*/
public static final long DEFAULT_HBASE_CLIENT_SCANNER_MAX_RESULT_SIZE = 2 * 1024 * 1024;
{quote}
> should not setMaxResultSize on hbase scan as it might cause incorrect answers
> -----------------------------------------------------------------------------
>
> Key: KYLIN-1545
> URL: https://issues.apache.org/jira/browse/KYLIN-1545
> Project: Kylin
> Issue Type: Bug
> Reporter: hongbin ma
> Assignee: hongbin ma
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)