<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6001.18226" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=675521822-04062009><FONT face="Lucida Sans" color=#000080
size=2>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.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000080 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mondrian-bounces@pentaho.org
[mailto:mondrian-bounces@pentaho.org] <B>On Behalf Of </B>Matt
Campbell<BR><B>Sent:</B> Thursday, June 04, 2009 6:00 AM<BR><B>To:</B>
Mondrian developer mailing list<BR><B>Subject:</B> [Mondrian] Scoped solve
order / Aggregate<BR></FONT><BR></DIV>
<DIV></DIV><BR>
<DIV>I noticed today that Scoped solve order is broken with Aggregate().
If mondrian.rolap.SolveOrderMode=scoped, then the following query
will fail:</DIV>
<DIV><BR></DIV>
<DIV>
<DIV>with member [marital status].agg as 'Aggregate([marital status].[marital
status].members)'</DIV>
<DIV>select crossjoin( {Gender.Gender.M}, {[marital status].[marital
status].members, [marital status].agg} ) on 0, { measures.[profit
growth] } on 1 from sales;</DIV>
<DIV><BR></DIV>
<DIV>This throws the exception:</DIV>
<DIV> mondrian.olap.fun.MondrianEvaluationException: Could not find an
aggregator in the current evaluation context</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>I'll look into it some more here, but I'm curious if anyone knows of
recent checkins that might be
responsible.</DIV></DIV></BLOCKQUOTE></BODY></HTML>