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

JdbcSchema.setSchemaName() not useful

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Severity: Medium
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Aggregation Tables
    • 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

      setSchemaName(String) is intended to restrict the scan for candidate aggregation tables to just the schema specified.

      This functionality is not useful however because the way that aggregation tables are loaded, it is not possible to call the setSchemaName() method before the aggregation tables are scanned for. Thus, there is no way to limit the search for aggregation tables to just one schema.

      Further, it is not possible to create a JdbcSchema.Factory instance outside of the mondrian.rolap.aggmatcher package because the required methods are not visible outside the package, effectively making the Factory interface useless.

      If it was possible to create an instance of the Factory outside of the package, the 'custom' factory instance could setSchemaName(String) before the value was used in the loadTables().

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            rlear rlear
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: