[Mondrian] Better understanding of hierarchies without an All Member

Pedro Alves pmgalves at gmail.com
Fri May 9 15:44:39 EDT 2014


That's a huge performance hog. I looked at it in the past, and my guess was
that w/o an all member, it wouldnt be able to define what context to use

For me, would be logical to define a "defaultMember" and stick to that if
none defined.

As is, it's unusable....

On Friday, May 9, 2014, Will Gorman <wgorman at pentaho.com> wrote:

> Hi folks,
> I’m working with a schema that has defined a number of hierarchies that do
> not have an all member.  I’m running into some areas of the code that I’m
> not that familiar with.  I see in RolapResult, we load all the members of
> hierarchies without an all member through loadSpecialMembers(), and then
> use those members while evaluating the slicer and axis.  Shouldn’t these
> resolutions only care about the default member of the hierarchy?   Why are
> all the members at play during this portion of the algorithm?
> Thanks,
> Will
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20140509/c48b96a5/attachment.html 

More information about the Mondrian mailing list