Hi Sarnath,
You are welcome.
Kylin has dictionary for all dimensions, so id vs name is no matter,
just pick up one or both best for your case.
So memory consumption between denormalized and normalized should just
be a litter bit different.
Hope such explain could help you.
Thanks.
Best Regards!
---------------------
Luke Han
On Thu, Jul 9, 2015 at 9:20 PM, Sarnath <[email protected]> wrote:
> Hi Luke,
> Thanks. This is good to know.
> Also, Will use of denormalized tables result in more memory consumption in
> kylin than maintaining a normalized one?
> E.g. It is cheaper to store a country ID than country name.
> (Or) will kylin build an internal set of IDs and not store the strings
> directly?
> Thanks
> Best,
> Sarnath
> On Jul 9, 2015 5:40 PM, "Luke Han" <[email protected]> wrote:
>
> > HI Sarnath,
> > Kylin supports denormalized table, you can generate one flat file and
> > just use it as source to build cube.
> >
> > To leverage Star Schema is easy for people to understand data model,
> > most of cases are using star schema to store data and so on.
> >
> > Thanks.
> >
> > Luke
> >
> >
> > Best Regards!
> > ---------------------
> >
> > Luke Han
> >
> > On Thu, Jul 9, 2015 at 8:01 PM, Sarnath <[email protected]> wrote:
> >
> > > Hi,
> > > Can kylin work with denormalized tables? Or is star schema mandatory?
> > > Why I ask this is : in hadoop world most tables are denormalized..
> > > Is there any motivation behind star schema?
> > > Best,
> > > Sarnath
> > >
> >
>
