Uploaded image for project: 'Community Data Access'
  1. Community Data Access
  2. CDA-209

CDA Query Keeps Older Data In Cache After Changes to DB and Clearing Mondrian and CDA Cache

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Severity: Urgent
    • Resolution: Duplicate
    • Affects Version/s: 6.1.0.9 GA
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Story Points:
      0
    • 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

      In the attached video you can see using Steel Wheels in PostgreSQL the initial Analyzer report and CDA query show the status with the value of "In Process"

      https://pentaho.box.com/s/ibfdbgzthrbdis8ujrl5h4tsnen5ulni

      Then we changed the value of the status "In Process" to "Processing" by running an update statement at the database level; after clearing the Mondrian Schema and CDA Cache you can see the Analyzer report reflects the new change in the status by showing "Processing" however the CDA query does not reflect the new value.

      The only way the new value is reflected on the CDA query is to restart the BA Server

      In order to reproduce please use the attached materials

        Attachments

        1. Cda_Cache_Issue.xanalyzer.zip
          2 kB
        2. CDA_Issue.cda.zip
          1 kB
        3. pSteelWheels.mondrian.xml
          7 kB
        4. sampledata.sql
          742 kB

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              clopez Carlos Lopez
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: