Pentaho Analysis - Mondrian
  1. Pentaho Analysis - Mondrian
  2. MONDRIAN-902

mondrian populating the same members on both axes

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Unknown Unknown
    • Resolution: Fixed
    • Affects Version/s: 3.2.0 GA (3.6.0 GA Suite Release)
    • Component/s: None
    • Labels:
      None
    • QA Validation Status:
      Validated by QA

      Description

      I would have filed a JIRA but I can't even describe what is happening, so I just post it on this ML.

      We have discovered a very weird behaviour in mondrian when we execute the following MDX statement on foodmart:
      SELECT
      NON EMPTY CrossJoin([Education Level].[Education Level].Members, CrossJoin([Product].[Product Family].Members, [Store].[Store State].Members)) ON COLUMNS,
      NON EMPTY CrossJoin([Promotions].[Promotion Name].Members, [Marital Status].[Marital Status].Members) ON ROWS
      FROM [Warehouse and Sales]

      When i execute this i get a result that looks like this: http://i.imgur.com/eK1KH.jpg - also attached to this JIRA (this is executed in saiku but i have reproduced the same issue with PDI (using a 3-3-SNAPSHOT and olap4j-0.9.9-SNAPSHOT)
      It seems like mondrian is populating the same members on both axes

      When I add a Measure to the ROWS axis, it works correctly, however if I add it to COLUMNS it adds the measure to the columns but shows the same faulty resultset as in the first query result

      I've never come along a similar error and this is the only combination i found so far that produces this behaviour.

        Activity

        Hide
        Julian Hyde added a comment -
        Fixed in change 14151. Will be in mondrian-3.3. It happened that both axes generated a query with the same constraints, so the second axis found and used the results of the first axis. What was missing was a notion of the set of dimensions projected, in addition to the constraints.
        Show
        Julian Hyde added a comment - Fixed in change 14151. Will be in mondrian-3.3. It happened that both axes generated a query with the same constraints, so the second axis found and used the results of the first axis. What was missing was a notion of the set of dimensions projected, in addition to the constraints.
        Hide
        Golda David added a comment -
        In analyzer all measures need to be pulled over to a numbers field and we never have problem having the same measure on both axis.

        This issue is resole.d
        I tested using the mondrian 3.3 build from Oct 4th 2011
        Show
        Golda David added a comment - In analyzer all measures need to be pulled over to a numbers field and we never have problem having the same measure on both axis. This issue is resole.d I tested using the mondrian 3.3 build from Oct 4th 2011
        Hide
        Golda David added a comment -
        Modrian does not populate both members on the same axis in an analyzer report.
        Show
        Golda David added a comment - Modrian does not populate both members on the same axis in an analyzer report.

          People

          • Assignee:
            Golda David
            Reporter:
            Paul Stoellberger
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: