[Mondrian] Problem with aggregate tables..

Ati Rosselet ati.rosselet at gmail.com
Thu Oct 18 14:44:38 EDT 2007

Something is fishy... If I reverse the order of the two dimensions in the
schema, then the opposite occurs.. almost as if the first dimension "owns"
the aggregate table, and the subsequent dimension is not allowed to use it,
or simply does not find it in the aggregate table list.....

Foodmart.. hmm.. okay... time to create that db again then.. *sigh* :)

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
>  ------------------------------
> *From:* mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org]
> *On Behalf Of *Ati Rosselet
> *Sent:* Thursday, October 18, 2007 2:58 AM
> *To:* mondrian at pentaho.org
> *Subject:* [Mondrian] Problem with aggregate tables..
> Hi, I'll try to be clear here.
> We are running mondrian 2.4 with the Aggregate query generation turned on
> at the moment and we have the following, odd situation:
> We have 2 dimensions (Period and Period2), both of which reference the
> same set of id's
> We have also created the appropriate aggregate table for a certain level,
> and all works fine.. kind of.
> The problem is that when the query using "Period" runs, the aggregate
> table we created is shown on the console, and the database logs show that it
> used, and consequently everything is FAST!!  However, when using the
> "Period2" dimension, although the EXACT SAME table is shown on the console
> as a suggested aggregate table..  it is never used.
> I could understand if it was finding a 'better' table and using that
> instead, but rather it is not using any aggregate table at all.  ??????
> What situation could cause the processing of an MDX query to list
> "suggested" tables, and then NOT use one of them if it exists?
> We've been trying, tweaking etc.. and no change..   at a complete loss
> here... any ideas?
> Cheers
> Ati
> (Julian... just found the new mailing list  - thnx... did you shut down
> the old spamful one?)
> _______________________________________________
> Mondrian mailing list
> Mondrian at pentaho.org
> http://lists.pentaho.org/mailman/listinfo/mondrian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20071018/94aff24a/attachment.html 

More information about the Mondrian mailing list