You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Dayue Gao (JIRA)" <ji...@apache.org> on 2017/01/13 12:28:26 UTC

[jira] [Resolved] (KYLIN-2386) Revert KYLIN-2349 and KYLIN-2353

     [ https://issues.apache.org/jira/browse/KYLIN-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dayue Gao resolved KYLIN-2386.
------------------------------
       Resolution: Fixed
    Fix Version/s: v2.0.0

commit https://github.com/apache/kylin/commit/4b977215186281908a8c29741128242146a2b934

> Revert KYLIN-2349 and KYLIN-2353
> --------------------------------
>
>                 Key: KYLIN-2386
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2386
>             Project: Kylin
>          Issue Type: Task
>          Components: Metadata
>    Affects Versions: v2.0.0
>            Reporter: Dayue Gao
>            Assignee: Dayue Gao
>             Fix For: v2.0.0
>
>
> In KYLIN-2349 and KYLIN-2353, we changed the storage format of BitmapCounter for better performance. In the new format, cardinality and serialized size are recorded in the header part. This enables us to retrieve those information without deserialize the whole data.
> However, cardinality and serialized size can be quickly calculated just from the header of [roaring format|https://github.com/RoaringBitmap/RoaringFormatSpec/]. Performance tests show that we could achieve the same performance gain without the format change. The benefits are
> * there is no need for user to rebuild existing cube to get better performance
> * there is no need for developer to maintain two formats and deal with compatibility issues



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