Mailing-List: contact dev-help@kylin.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kylin.apache.org
Date: Fri, 13 Jan 2017 11:17:26 +0000 (UTC)
From: "Dayue Gao (JIRA)" <jira@apache.org>
To: dev@kylin.apache.org
Message-ID: <JIRA.13034603.1484306212000.1340.1484306246390@Atlassian.JIRA>
In-Reply-To: <JIRA.13034603.1484306212000@Atlassian.JIRA>
References: <JIRA.13034603.1484306212000@Atlassian.JIRA> <JIRA.13034603.1484306212957@jira-lw-us.apache.org>
Subject: [jira] [Created] (KYLIN-2386) Revert KYLIN-2349 and KYLIN-2353
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 13 Jan 2017 11:17:30 -0000

Dayue Gao created KYLIN-2386:
--------------------------------

             Summary: 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


In KYLIN-2349 and KYLIN-2353, we optimized performance of BitmapCounter by changing its storage format. Cardinality and serialized size are recorded in the header of the new format, enables us to retrieve those information without deserialize the data.

In fact, 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 boost without the format change of BitmapCounter. The benefits are
* no need to rebuild existing cube to get better performance
* no need to maintain two formats and deal with compatibility issues


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