Uploaded image for project: 'Pentaho Analysis - Mondrian'
  1. Pentaho Analysis - Mondrian
  2. MONDRIAN-568

If two cubes have dimension with same name, mondrian treats grant to one as grant to other

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Severity: Medium
    • Resolution: Fixed
    • Affects Version/s: 3.1 GA
    • Component/s: None
    • Labels:
      None
    • Notice:
      When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.

      Description

      Email from Alexander Korsukov:

      See RoleImpl.getAccess(Dimension)

      Dimension compared with dimensions from all cubes. I catch following problem.

      Have cube [CubeA] with measures [Measures].[MA1] and [Measures].[MA2] and cube [CubeB]. Define roles:

      <Role name="RoleA">
      <SchemaGrant access="none">
      <CubeGrant cube="CubeA" access="all">
      <HierarchyGrant hierarchy="[Measures]" access="custom">
      <MemberGrant member="[Measures].[MA1]" access="all"/>
      </HierarchyGrant>
      </CubeGrant>
      </SchemaGrant>
      </Role>

      <Role name="RoleB">
      <SchemaGrant access="none">
      <CubeGrant cube="CubeB" access="all"/>
      </SchemaGrant>
      </Role>

      When create mondrian connection with Role=RoleA, have access only to [Measures].[MA1]. When create mondrian connection with Role=RoleA,RoleB, have access to all measures from [CubeA]. Why? Because when check role RoleB mondrian found [Measure] dimension of [CubeB] then equals to [Measure] dimension of [CubeA] and therefore get access to all members of [Measure].

      See rest of thread: http://forums.pentaho.org/showthread.php?t=70624

        Attachments

          Activity

            People

            Assignee:
            jcornelius Jared Cornelius (Inactive)
            Reporter:
            jhyde Julian Hyde (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: