kylin-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (KYLIN-3461) " refresh-cube-signature" not updating cube signature as expected
Date Wed, 01 Aug 2018 10:59:00 GMT


ASF GitHub Bot commented on KYLIN-3461:

asfgit commented on issue #183: KYLIN-3461 refresh-cube-signature not updating
cube sign…
   Can one of the admins verify this patch?

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> " refresh-cube-signature" not updating cube signature as expected 
> ------------------------------------------------------------------------------
>                 Key: KYLIN-3461
>                 URL:
>             Project: Kylin
>          Issue Type: Bug
>          Components: Client - CLI
>    Affects Versions: v2.3.2
>            Reporter: Yuan Weizhao
>            Priority: Critical
>         Attachments: build-cube-log.png, log-2-calculate-signature-when-refresh-cube-signature.log,
log1-calculate-signature-when-building.log, refresh-cube-signature-log.png
> Recently I upgraded kylin from 2.3.1 to 2.3.2, and when I tried to build a cube, the
Web UI told me that my cube signature is inconsistent, and suggested that I use the
script to refresh all cube signatures. 
>  I did what I was told to, but as I can read from the log, the script didn't update any
cube signature, and I still received the same error message when I retried to build the cube.
>  I did some digging on the source code, and add some logging statements, re-packaged
kylin and deployed the more-logging version. I found that when kylin refreshes cube signatures
and build new cube segments, it always check whether the cube signature equals to the calculated
signature which is calculated by method org.apache.kylin.cube.model.CubeDesc#calculateSignature().
> And as I observed from the log, this method return DIFFERENT RESULT under the above two
> The Difference lies in that when building cube segments invokes calculateSignature(),
it will add "encoding_version" into the "rowkey" json string.

This message was sent by Atlassian JIRA

View raw message