Pentaho Reporting and Pentaho Report Designer
  1. Pentaho Reporting and Pentaho Report Designer
  2. PRD-4004

As a reporting user, I want the ability to declare additional mondrian connection properties (like 'jdbcconnectionuid') on a mondrian connection

    Details

    • 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.
    • QA Validation Status:
      Validated by QA

      Description

      When run in standalone == false (inside BI server), PRD disregards the catalog properties that are present in datasources.xml. It builds a new connection string with a small subset of those properties (in PentahoCubeProvider).

      This should be changed so that all properties in the catalog string are used to build the Mondrian Connection. This is relevant so that PRD can use the jdbcconnectionuid property newly introduced to Mondrian and, subsequently, share the Mondrian cache with the other platform components.

      We propose that the PentahoCubeProvider class/mechanism should be replaced with a PentahoCatalogStringProvider that will create a catalog string with all the properties in datasources.xml

        Issue Links

          Activity

          Hide
          Kurtis Cruzada added a comment -
          This was addressed in 3.9.1.
          Show
          Kurtis Cruzada added a comment - This was addressed in 3.9.1.
          Hide
          Pedro Alves added a comment -
          Actually, this issue should be reopened. It still disregards connection properties, what was done in PRD was allow the user to explicitly pass properties. The user still has to replicate the properties that already exist in olap/datasources.xml
          Show
          Pedro Alves added a comment - Actually, this issue should be reopened. It still disregards connection properties, what was done in PRD was allow the user to explicitly pass properties. The user still has to replicate the properties that already exist in olap/datasources.xml
          Hide
          Will Gorman added a comment -
          Reopening based on Pedro's comments, Brandon, can you double check that this capability wasn't implemented?

          Thanks,

          Will
          Show
          Will Gorman added a comment - Reopening based on Pedro's comments, Brandon, can you double check that this capability wasn't implemented? Thanks, Will
          Hide
          Thomas Morgner added a comment -
          PRD does not access 'datasources.xml' as this is a pure server side file and it is not exposed to remote clients. If you are ONLY talking about "reports run in the server" then please change the title of the case. PRD means: Running outside of the server inside the product called "Pentaho Report Designer".
          Show
          Thomas Morgner added a comment - PRD does not access 'datasources.xml' as this is a pure server side file and it is not exposed to remote clients. If you are ONLY talking about "reports run in the server" then please change the title of the case. PRD means: Running outside of the server inside the product called "Pentaho Report Designer".
          Hide
          Pedro Alves added a comment -
          Thomas, you are absolutely correct. I always meant the reporting plugin , prd was an abuse of language
          Show
          Pedro Alves added a comment - Thomas, you are absolutely correct. I always meant the reporting plugin , prd was an abuse of language
          Hide
          Thomas Morgner added a comment -
          Changed this case once more to reflect the work that we actually did based on the original description. This way, the commit log and the change-log for the PRD-3.9.1 release are accurately reflecting the features we added.
          I created a follow-up case PRD-4140 to solve the implicit problem stated by this case: That we want to reuse existing connections on the server instead of having manual connection definitions inside a PRPT file.
          Show
          Thomas Morgner added a comment - Changed this case once more to reflect the work that we actually did based on the original description. This way, the commit log and the change-log for the PRD-3 .9.1 release are accurately reflecting the features we added. I created a follow-up case PRD-4140 to solve the implicit problem stated by this case: That we want to reuse existing connections on the server instead of having manual connection definitions inside a PRPT file.
          Hide
          Thomas Morgner added a comment -
          No checkin, just walking through the work-flow.
          Show
          Thomas Morgner added a comment - No checkin, just walking through the work-flow.

            People

            • Assignee:
              Kurtis Cruzada
              Reporter:
              Pedro Vale
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: