[ https://issues.jboss.org/browse/TEIID-2469?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2469: --------------------------------------- Added the initial implementation that ties internal mat views with the external logic. If the allow management property is used on an internal materialized view, then it will be pre-loaded and will have it's refresh done via the MaterializationManager - although this logic is weaker than what I would like and generally uses a fixed ttl, such that any modification of the ttl property at runtime won't be effective. There appeared to be several issues with the MaterializationManager that this check in attempted to address: 1. how tasks accessed in the map was inconsistent, for example removal just based upon the task rather than looking up first by vdb key 2. the use of a timer should be avoided when possible, also it's possible to consolidate in embedded several asynch thread pools 3. there should be a way to execute a query asynchly, as having a thread waiting on future.get isn't necessary for just a refresh. however I only made this change for the internal case 4. the external logic didn't seem to keep rescheduling the next load in all cases - for example if the mat view is currently loading, then the task no longer repeats. 5. there was duplication in the executeQuery code between the two implementations -- This message was sent by Atlassian JIRA (v6.3.15#6346)