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

Add Schema attribute to AggName / AggPattern definitions to restrict search



    • Type: New Feature
    • Status: Open
    • Severity: High
    • Resolution: Unresolved
    • Affects Version/s: 3.0.5
    • Fix Version/s: Backlog
    • Component/s: None
    • Labels:
    • 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.


      As I explained in the EE forum (http://forums.pentaho.org/showthread.php?t=68902) it is not possible to restrict the scan for Aggregation Tables to a specific schema.
      I'm working a lot with Oracle DB's with many different Schema's with hundreds of tables/views in there. Mondrian's scan through the data dictionary to find Agg Tables takes a lot of time (couple of mins at least). The scan for agg tables happen everytime a MDX query is executed, so this is an absolute critical blocker for using agg tables in an large Oracle DWH.

      Rolf has proposed a change in the API (MONDRIAN-511). I can see the point of not doing the change in there. Julian suggested a new Schema attribute for AggName, which sounds quite reasonable. However, AggName definitions would add a lot of verbose lines to the Cube definition and is not as flexible as defining an AggPattern. With only a few lines you can easily do a transparent definition of the agg tables.
      So I propose adding a Schema Attribute to AggPattern and optionally to AggName (thats used by PAD, so I think it would be good to have that in there as well)




            Unassigned Unassigned
            pstoellberger Paul Stoellberger
            6 Vote for this issue
            4 Start watching this issue