[Mondrian] Aggregate tables and column / nameColumn - how is it supposed to work
jhyde at pentaho.com
Tue Nov 10 12:21:36 EST 2009
Aggregate tables are mainly intended to speed up accesses to cells, not
accesses to members. We have enhanced them to support various member
queries, but the support is spotty. This sounds like a reasonable case and
you should log a feature request.
> -----Original Message-----
> From: mondrian-bounces at pentaho.org
> [mailto:mondrian-bounces at pentaho.org] On Behalf Of Pedro Alves
> Sent: Tuesday, November 10, 2009 4:13 AM
> To: Mondrian developer mailing list
> Subject: [Mondrian] Aggregate tables and column / nameColumn
> - how is it supposed to work
> Hello everyone.
> How are aggregate tables supposed to work when we use the nameColumn
> for a level that has <level name="[MyLevel]" column="id"
> nameColumn="desc"... /> I noticed that RolapStar creates 2 different
> entries: MyLevel (2) and MyLevel (Key) (3);
> Problem: When the agg tables are created (per PAD suggestion)
> only the
> mylevelid_Key column is created. This means the AggStar will contain
> dimension (3), but when I create a query like MyLevel.Children it's
> querying for (2); Result: fact table gets hit.
> What am I missing?
> ps: Should I be using nameColumn at all? What's the
> difference between
> this as caption?
> Mondrian mailing list
> Mondrian at pentaho.org
More information about the Mondrian