Hitachi Vantara Pentaho Community Forums
Results 1 to 2 of 2

Thread: [Mondrian] Predicate optimization parameter

  1. #1
    Guest

    Default [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?



    Mike/Raghu






    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

  2. #2
    Julian Hyde Guest

    Default RE: [Mondrian] Predicate optimization parameter

    No objections to you making that a property. Please follow the process for
    adding a property, described in
    http://mondrian.pentaho.org/api/mond...roperties.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.

    Julian



    _____

    From: mondrian-bounces (AT) pentaho (DOT) org [mailto:mondrian-bounces (AT) pentaho (DOT) org] On
    Behalf Of michael.pflug (AT) thomson (DOT) com
    Sent: Wednesday, October 17, 2007 11:45 AM
    To: mondrian (AT) pentaho (DOT) 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?



    Mike/Raghu






    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.