[Mondrian] Question on Aggregation

Richard Emberson remberson at edgedynamics.com
Tue May 29 10:18:12 EDT 2007

The BitKey is relatively new. It is used as a key to a Map.
Not too long ago, what was used as the key was a List
containing all of the column's unique names - as such, the
BitKey is an optimization. When the List was replaced with
the BitKey, a complete refactoring did not take place,
rather what was attempted was only a modest code change;
hence the disconnect between where the BitKey is created
and given to to the Aggregate in its constructor and
where the columns are loaded.
Mondrian is and will always be a work in progress.
Developers are welcome to contribute.


Thiyagu Palanisamy wrote:
> Hi,
>  We are currently looking on ways to optimize the usage of 
> Synchronization block around aggregation load.
>  Aggregation class has "constrainedColumnsBitKey" and "columns" fields. 
> Our understanding is both of them represent the same columns list, in 
> case constrainedColumnsBitKey and columns differ can someone give an 
> example of when this could happen?
>  We are wondering why "constrainedColumnsBitKey" initialized in 
> constructor and "columns" initialized in load().
> Thanks,
> Thiyagu & Tushar
> ------------------------------------------------------------------------
> _______________________________________________
> Mondrian mailing list
> Mondrian at pentaho.org
> http://lists.pentaho.org/mailman/listinfo/mondrian

Quis custodiet ipsos custodes:
This email message is for the sole use of the intended recipient(s) and
may contain confidential information.  Any unauthorized review, use,
disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and destroy all
copies of the original message.

More information about the Mondrian mailing list