[Mondrian] Scoped solve order / Aggregate

Julian Hyde jhyde at pentaho.com
Thu Jun 4 21:11:32 EDT 2009

Look at my change 12728, which changed the part of the query lifecycle when
solve order mode is read from the properties file. It's possible that this
is responsible. This change improved performance significantly, and is
correct as far as I know, so I would like to hear a justification before you
reverse it.


From: mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org] On
Behalf Of Matt Campbell
Sent: Thursday, June 04, 2009 6:00 AM
To: Mondrian developer mailing list
Subject: [Mondrian] Scoped solve order / Aggregate

I noticed today that Scoped solve order is broken with Aggregate().  If
mondrian.rolap.SolveOrderMode=scoped, then the following query will fail:

with member [marital status].agg as 'Aggregate([marital status].[marital
select   crossjoin( {Gender.Gender.M}, {[marital status].[marital
status].members, [marital status].agg} )  on 0, { measures.[profit growth] }
on 1 from sales;

This throws the exception:
 mondrian.olap.fun.MondrianEvaluationException: Could not find an aggregator
in the current evaluation context

I'll look into it some more here, but I'm curious if anyone knows of recent
checkins that might be responsible.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20090604/aebec75b/attachment.html 

More information about the Mondrian mailing list