[
https://issues.jboss.org/browse/TEIID-5427?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-5427:
-------------------------------------
+1, although we implemented this originally for maximum flexibility in terms of
cachebility, it did not span out to be a distinct feature. Realistically, it is hard to
find architecture designs that are being cached actively at the session level for
individual user level, even if there are they typically for a very short duration of time.
I feel Infinispan like instance caching is more suitable in situations like this.
I would even go further simplification to remove the vdb scoped distinction too.
Basically, we are trying to guard against the schema evolution here more than anything.
Remove session/user scoped materialized views
---------------------------------------------
Key: TEIID-5427
URL:
https://issues.jboss.org/browse/TEIID-5427
Project: Teiid
Issue Type: Task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.1
TEIID-2507 added session scoped materialized views - which are now not well aligned with
any other materialization strategy. They have to be unmanaged and internal only. It
would be best to completely remove the feature and recommend instead that users create
global temporary tables instead.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)