You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2016/12/02 03:40:58 UTC

[jira] [Created] (KYLIN-2243) TopN memory estimation is inaccurate in some cases

Shaofeng SHI created KYLIN-2243:
-----------------------------------

             Summary: TopN memory estimation is inaccurate in some cases
                 Key: KYLIN-2243
                 URL: https://issues.apache.org/jira/browse/KYLIN-2243
             Project: Kylin
          Issue Type: Bug
            Reporter: Shaofeng SHI
             Fix For: Backlog


TopNCounterSerializer.maxLength() and TopNCounterSerializer.getStorageBytesEstimate() might be inaccurate, especially when there are multiple "group by" columns in one TopN measure and some uses long bytes encoding like "fixed_length:16"

The inaccurate estimation may cause memory issue when using in-mem cubing, and will cause the estimation on final cube size inaccurate.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)