From issues-return-16110-archive-asf-public=cust-asf.ponee.io@kylin.apache.org Fri Feb 2 20:59:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 99CB0180608 for ; Fri, 2 Feb 2018 20:59:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 89576160C57; Fri, 2 Feb 2018 19:59:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D25D1160C25 for ; Fri, 2 Feb 2018 20:59:03 +0100 (CET) Received: (qmail 22213 invoked by uid 500); 2 Feb 2018 19:59:03 -0000 Mailing-List: contact issues-help@kylin.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kylin.apache.org Delivered-To: mailing list issues@kylin.apache.org Received: (qmail 22204 invoked by uid 99); 2 Feb 2018 19:59:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Feb 2018 19:59:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 87685198C46 for ; Fri, 2 Feb 2018 19:59:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id DJTwogru-mlF for ; Fri, 2 Feb 2018 19:59:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 146675F5FB for ; Fri, 2 Feb 2018 19:59:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 56E4AE02F1 for ; Fri, 2 Feb 2018 19:59:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 14F4721E84 for ; Fri, 2 Feb 2018 19:59:00 +0000 (UTC) Date: Fri, 2 Feb 2018 19:59:00 +0000 (UTC) From: "mathias kluba (JIRA)" To: issues@kylin.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KYLIN-3138) cuboids on-demand build MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KYLIN-3138?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1635= 0880#comment-16350880 ]=20 mathias kluba commented on KYLIN-3138: -------------------------------------- I also have that issue with cube with large amount of dimensions (ex: 300). I know we can optimize the cube ([http://kylin.apache.org/docs21/howto/howt= o_optimize_cubes.html)]=C2=A0but it requires to think upfront.=C2=A0 It would be nice to build the 1st layer only, and aggregate "on the fly" du= ring query time for a missing cuboid. =C2=A0 > cuboids on-demand build > ----------------------- > > Key: KYLIN-3138 > URL: https://issues.apache.org/jira/browse/KYLIN-3138 > Project: Kylin > Issue Type: New Feature > Components: Job Engine, Query Engine, Spark Engine > Affects Versions: v2.2.0, v2.3.0 > Reporter: Ruslan Dautkhanov > Assignee: Shaofeng SHI > Priority: Critical > > We just started using Kylin and quite like it so far. > Although some of the datasets we have are quite wide to even consider for= OLAP cubing. > Unless those cuboids will be built on-demand. > I know some commercial non-open source products do this successfully.=20 > This idea is to build a cuboid only when a user actually needs it.=20 > So for example, our BI dashboards does a certain rollup, so then a SQL > query hits Kylin backend. Kylin realizes it hasn't built that particular = cuboid just yet, > so immediately starts building it. Users has to wait a bit longer first t= ime > it request that combination of dimensions. But all other requests or requ= ests=20 > of other users will be fast from that point on. > Kylin (or any other OLAP solution) wouldn't be feasible to use on very wi= de datasets=20 > unless this on-demand functionality is implemented. For example, some dat= asets we have have 100-200 dimensions. And we don't know up front rollups u= sers would want to do. > Suggesting to have a new dimension build rule "lazy / on-demand". All pre= vious rules apply. This new rule type would mean, a cuboid for a particular= set of dimensions wouldn't be built up-front if it's marked as "lazy / on-= demand".=20 > Thoughts / ideas? -- This message was sent by Atlassian JIRA (v7.6.3#76005)