Hitachi Vantara Pentaho Community Forums
Results 1 to 5 of 5

Thread: Collapsed Aggregate Table problem

  1. #1
    Join Date
    Jan 2007
    Posts
    25

    Default Collapsed Aggregate Table problem

    Hi.

    I am new using aggregate tables, i have a fact table with id_geography, and geography dimension with desc_country, desc_region, desc_departament, desc_city and id_geography.

    i want to collapse geography dimension , using in agg table only desc_country and desc_region.

    in the mondrian log i have the sql:

    select
    "geography"."desc_region" as "c0"
    from
    "agg_1_fact_table" as "agg_1_fact_table",
    "geography" as "geography"
    where
    "agg_1_fact_table"."desc_country" = 'Canada' and
    ("geography"."desc_country" = 'Canada')
    group by
    "geography"."desc_region"
    order by
    "geography"."desc_region" ASC

    My question is: why if the description is in the aggregate table, mondrian uses geography table too, if the field names are equal?

    there is any way to have an sql that not use geography dimension? only aggregate table?

    Thanks for any help

  2. #2

    Unhappy

    Hi,
    I have the same problem. Don't understand why mondrian is using the dimension table, since all the information is in the fact table.
    The query is slow because there is no join operation defined between the two tables.
    I found an odd workaround. Create a aggregate table with the collapse dimension and the fact columns. But this can't be the answer.

    Please response.. this is an important issue.

    Thanks,
    Carlos Dias

  3. #3

    Default

    Another important issue... and this is really important.
    Any other user has this problem???

    Julian Hyde, can you answer to this one too?

    Thanks,
    Carlos Dias

  4. #4

    Unhappy

    Back to this post again...
    This is a very important issue...

    Anybody can help?

    Carlos Dias

  5. #5

    Default

    In the Mondrian documentation:
    The SQL generated for a MDX query for which this aggregate table can be used, would no longer refer to the time dimension's table but rather all time related information would be gotten from the aggregate table.
    With this I can conclude that the behavior described below is a bug. Please confirm.


    Carlos Dias

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.