As today's DW/BI world, Hierarchy Dimension is still very popular and common for BI experts and users, like most of traditional and modern products doing. I don't think it will confuse users especially when they design cubes.
So keep the same concept is very important for user to adopt new stuff, here is Kylin, on new tech stack. Whatever backend setting will be, the user facing term, concept should always keep same with existing one as much as possible:) For documentation, there's terminology page would like to recommend newbie to go through first: http://kylin.incubator.apache.org/docs/gettingstarted/terminology.html There's some enhancement of current UI and tutorial documentation will come, but I don't think it make sense for a project to draft all basic and common concept and terms everywhere:-) Thanks. Best Regards! --------------------- Luke Han On Tue, Sep 22, 2015 at 4:15 AM, Patrick McAnneny < [email protected]> wrote: > I found it confusing initially until I read about how it is mostly a method > of optimising the cube (rather than a separate type of dimension that would > be queried differently). It makes a lot of sense now that I understand, but > perhaps a little bit more documentation would help others starting out. (it > is not covered in the cube construction slides) > > Not a huge deal though > > On Mon, Sep 21, 2015 at 3:21 PM, Julian Hyde <[email protected]> wrote: > > > Yes, hierarchies may be a useful organizing concept. I claim that > > hierarchies are separate things: (1) navigation paths for a UI, (2) > > statistical patterns in data access. Conversations like this one are > > evidence that — at least for some people — hierarchies are confusing. So, > > keep them as a user concept only if they make life simpler for the > majority > > of users. > > > > Julian > > > > > > > On Sep 21, 2015, at 2:34 AM, Li Yang <[email protected]> wrote: > > > > > > @Julian, plan to refactor the underlying aggregation group in Q4. Will > > drop > > > hierarchy concept in the backend, however in the frontend for ease of > > > understanding, may still call it hierarchy. :-) > > > > > > On Sat, Sep 19, 2015 at 2:40 AM, Patrick McAnneny < > > > [email protected]> wrote: > > > > > >> Great thread and great read. I see now that hierarchies are just a way > > to > > >> specify correlated dimensions for added efficiencies in cube > > architecture. > > >> I understand now. Thanks a lot! > > >> > > >> On Fri, Sep 18, 2015 at 1:08 PM, Julian Hyde <[email protected]> > wrote: > > >> > > >>> As I've said before[1] I don't think hierarchies add much to Kylin. > > >>> > > >>> Julian > > >>> > > >>> [1] > > >>> > > >> > > > http://mail-archives.apache.org/mod_mbox/kylin-dev/201506.mbox/%[email protected]%3E > > >>> > > >>> On Fri, Sep 18, 2015 at 9:18 AM, Patrick McAnneny > > >>> <[email protected]> wrote: > > >>>> So does a regular dimension though right? What's the difference > > >> between a > > >>>> singular hierarchy dimension and a regular dimension? The end > > resulting > > >>>> kylin sql would be the same (group by) right? Thanks for helping me > > >>>> understand! > > >>>> > > >>>> On Fri, Sep 18, 2015 at 12:01 PM, Sarnath <[email protected]> > wrote: > > >>>> > > >>>>> Hierarchy indicates that drill down is possible. > > >>>>> > > >>> > > >> > > > > >
