[Mondrian] Predicate optimization parameter

Julian Hyde julianhyde at speakeasy.net
Wed Oct 17 15:04:01 EDT 2007

No objections to you making that a property. Please follow the process for
adding a property, described in
http://mondrian.pentaho.org/api/mondrian/olap/MondrianProperties.html. Make
sure that the code does something sensible even if they give a stupid value
for the property (sensible includes giving an error message or defaulting to
a sensible value - your choice). Give the property a sensible name and a
description that a DBA - someone not necessarily familiar with mondrian
internals - could understand.


From: mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org] On
Behalf Of michael.pflug at thomson.com
Sent: Wednesday, October 17, 2007 11:45 AM
To: mondrian at pentaho.org
Subject: [Mondrian] Predicate optimization parameter

We are interested in adding a parameter in Mondiran.properties to take the
place of the hardcoded "aBloatLimit" variable that is currently set to 0.5
in the Aggregation.optimizePredicates method.   This parameter would allow
users to set the percentage of constrained cells to replace instead of being
forced into the hardcoded value of 50%.  Our specific reason for introducing
this parameter is that we have some queries in which this optimization is
querying more than required and is too costly.  Any comments?





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

More information about the Mondrian mailing list