Shaofeng SHI created KYLIN-2243:

             Summary: TopN memory estimation is inaccurate in some cases
                 Key: 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

Reply via email to