[Mondrian] Problem with aggregate tables..

Ati Rosselet ati.rosselet at gmail.com
Mon Oct 22 11:50:20 EDT 2007

>From delving into the Mondrian code, it appears to have something to do with
the following:

findTableWithLeftJoinCondition in RolapStar.java (called from
AggTableManager.java:483)  ..there is also a findTableWithLeftCondition
which seems to be identical.. and unused.. btw.. anyhow.. if there is a
column in the Star (here pillangoperiodid) that maps to more than one
dimension/hierarchy.. this function returns only the FIRST match...(creating
only one usage entry) leaving all other matching dimensions/hierarchies out
in the cold.   I assume there is more to this.. and will keep digging...
I'm guessing it may be a combination of this with the subsequent agg
matching (maybe again only checking for first somewhere?)


On 10/18/07, Julian Hyde <julianhyde at speakeasy.net> wrote:
>  Can you clarify? Period and Period2 are based on the same dimension
> table, with the same primary key, and the same foreign key from the fact
> table?
> At this point, it sounds like a bug in the aggregate table recognizer
> algorithm. There may be a bug logged already. If you can convert into
> a testcase on the foodmart schema that would help.
> Julian
> <http://lists.pentaho.org/mailman/listinfo/mondrian>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20071022/a4492f85/attachment.html 

More information about the Mondrian mailing list