[teiid-issues] [JBoss JIRA] Moved: (TEIID-1657) CLONE - EDS - refreshMatView does not work correctly for an internal materialized view when clustering is enabled

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins moved SOA-3127 to TEIID-1657:
--------------------------------------------

              Project: Teiid  (was: JBoss Enterprise SOA Platform)
                  Key: TEIID-1657  (was: SOA-3127)
    Affects Version/s: 7.1
                           (was: 5.1.0 GA)
          Component/s: Query Engine
                           (was: EDS)
             Security:     (was: Public)


> CLONE - EDS - refreshMatView does not work correctly for an internal materialized view when clustering is enabled
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: TEIID-1657
>                 URL: https://issues.jboss.org/browse/TEIID-1657
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 7.1
>            Reporter: Steven Hawkins
>
> The refreshMatView works as expected in a single node environment with 'teiid-cache-manager-jboss-beans-rename-me.xml'. Still in a single node environment, that function no longer refreshes the data with "teiid-cache-manager-jboss-beans.xml" enabled.
> To recreate:
> 1. Start up an EDS instance with a vdb deployed which has an internal materialized view (IMV).
> 2. Query SYSADMIN.MATVIEWS and verify LoadState = "NEEDS_LOADING"
> 3. Query the IMV to populate the cache.
> 4. Query SYSADMIN.MATVIEWS and verify LoadState = "LOADED". Note the value of the 'Updated' column
> 5. run "CALL SYSADMIN.refreshMatView('view name',false)"
> 6. Query SYSADMIN.MATVIEWS and verify LoadState = "LOADED". Note the value of the 'Updated' column
> 7. Query the IMV to see if it pulls from the source or cache
> Expected results: Steps 3 and 5 should trigger queries to the source. Step 7 should pull from the cache without going back to the source.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira