Kylin multiple cube issue from the same data model

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Kylin multiple cube issue from the same data model

elicer
Hi
I have some query on create multiple cube from the same data model,  I have a cute which build on a existing model(contains multiple aggregation group), Now I want to modify one of the aggregation group to add one more field, I don't want to impact the existing cube, So I created a new cube and only modified the impacted aggregation group, and rebuild the whole data with the new cute. Looks like only one table is available for one model, no matter how many cubes one data mode has.

Now the issue is, I am using JDBC to query the kylin data, when I initialize the jdbc connection, I need to specific the project name only, Then, How could I tell kylin, I need to fetch the data from the new cube? Looks like both the old and new cube data in the same kylin table only.
Reply | Threaded
Open this post in threaded view
|

Re: Kylin multiple cube issue from the same data model

Alberto Ramón
If there are more than one cube per proyect, the kylin optimizator choose
the best Cube to solve the query

On 19 May 2017 at 06:59, elicer <[hidden email]> wrote:

> Hi
> I have some query on create multiple cube from the same data model,  I have
> a cute which build on a existing model(contains multiple aggregation
> group),
> Now I want to modify one of the aggregation group to add one more field, I
> don't want to impact the existing cube, So I created a new cube and only
> modified the impacted aggregation group, and rebuild the whole data with
> the
> new cute. Looks like only one table is available for one model, no matter
> how many cubes one data mode has.
>
> Now the issue is, I am using JDBC to query the kylin data, when I
> initialize
> the jdbc connection, I need to specific the project name only, Then, How
> could I tell kylin, I need to fetch the data from the new cube? Looks like
> both the old and new cube data in the same kylin table only.
>
> --
> View this message in context: http://apache-kylin.74782.x6.
> nabble.com/Kylin-multiple-cube-issue-from-the-same-data-model-tp8032.html
> Sent from the Apache Kylin mailing list archive at Nabble.com.
>
Reply | Threaded
Open this post in threaded view
|

Re: Kylin multiple cube issue from the same data model

elicer
Thanks for your answer
If I have the same aggregation group in different cubes will it cause duplicate results?
Reply | Threaded
Open this post in threaded view
|

Re: Kylin multiple cube issue from the same data model

Alberto Ramón
One query only can be resolved with one cube

On 19 May 2017 at 07:58, elicer <[hidden email]> wrote:

> Thanks for your answer
> If I have the same aggregation group in different cubes will it cause
> duplicate results?
>
> --
> View this message in context: http://apache-kylin.74782.x6.
> nabble.com/Kylin-multiple-cube-issue-from-the-same-data-
> model-tp8032p8035.html
> Sent from the Apache Kylin mailing list archive at Nabble.com.
>