[
https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2584:
---------------------------------------
Can you suggest any alternatives, how I may be able to fix this?
You would make a more granular transaction around a an isloading status flag. Whatever
process can read the value as false and write it as true and commit in a txn block should
do the writing.
How about using a job scheduler like
http://quartz-scheduler.org/ for
this purpose of keeping the caches updated, that will also fix the above issue?
We've tossed quartz around before, but I can't say off hand if it's a good
fit. There are also ejb timers in as 7. I think what you are really getting at is
removing the maintenance concern from the processing logic. I think that is the right
approach with external materialization (internal too if it's re-targeted at something
that has a longer lifespan). The processing logic really should just be concerned if the
materialization table is in a readable state and have a known outcome if it's not
(wait, error, ignore and read anyway, etc.).
Add management features to materialization
------------------------------------------
Key: TEIID-2584
URL:
https://issues.jboss.org/browse/TEIID-2584
Project: Teiid
Issue Type: Feature Request
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.5
Currently Teiid supports internal and external materialization features. The internal is
managed completely by the Teiid query engine along with the infinispan cache.
External materialization is completely unmanaged and left out to the user to manage it
externally. This goals for this feature are unify the materialization logic for internal
and external, such that both are managed similarly irrespective of the type of
materialization chosen.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira