Which version you are using? There's bug relative to rowkey and hierarchy. Thanks.
Best Regards! --------------------- Luke Han On Mon, Jul 6, 2015 at 5:09 PM, Abhilash L L <[email protected]> wrote: > Hello, > > I was trying to understand hierarchical dimension usage. > > Lets say I have a fact table F with the structure, > > F > c1 > c2 > c3 > c4 > > And a hierarchical dimension H with the structure, > H > h1, > h2, > h3, > > The actual order is h2 > h3. > The join key is F.c4 = H.h1. > > I saw that, since h2,h3 form a hierarchical dimension, they become part of > row key.. so rowkey here is h2, h3 only. (This would help point / range > look ups) > > > In Kylin UI, when I try to fire a query, > > select ... > from F > join H on F.c4 = H.h1 > > I get an error saying F.c4 not found. > > What should a query look like which I can enter in Kylin UI as the above > query is not being accepted. > > Should the join key (in this case c4/h1) be part of the hierarchy as > h1>h2>h3 instead of only h2>h3? > > Regards, > Abhilash >
