[
https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin...
]
Ramesh Reddy edited comment on TEIID-5285 at 4/13/18 11:13 AM:
---------------------------------------------------------------
Yes, to both.
On transparency, in order for us to provide the updates transparently, we would need the
VDB, I am not looking at that as the user exercise. If the Teiid is in-line or as a
sidecar, the responsibility is on the user to create their domain entities which go to
Teiid instead of going to their DB
was (Author: rareddy):
Yes, to both.
Add high-level feature for redirection of updates
-------------------------------------------------
Key: TEIID-5285
URL:
https://issues.jboss.org/browse/TEIID-5285
Project: Teiid
Issue Type: Feature Request
Components: Query Engine, Teiid Spring Boot
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.3
In microservices testing it is desirable to test against production/live data but not
commit any updates. We should offer a simple solution that can defined by extension
metadata and enabled/disabled by a feature flag. We may need to make simplifying
assumptions about the scope (per session, per application, etc.) and durability of the
updates.
Under the covers this will be achieved by using views, update triggers, and a store for
the updates and when not enabled the expectation is that all operations should pass
through. However the application will be limited to using Teiid SQL and will be required
to use the Teiid or pg driver, or Teiid spring boot.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)