[teiid-issues] [JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates
[
https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-5285:
-------------------------------------
Yes, that looks like a good start. The assumption should be placed that the Main DB's
records are not being altered simultaneously by any other app.
Now we need to write a utility to generate VDB file, given the Main DB and Update DB
details. Including any resulting DDL for Update DB.
If we take the sidecar approach with this, which I think is appropriate, as it will give a
black box experience to the user, and will support different programming environments, we
need to generate an Appliance either using Spring Boot or WildFly-Swarm that given the
configuration about databases will configure rest automagically and expose a JDBC and ODBC
port.
Packaging this into OpenShift, I feel there are a few more knobs to make it look
seamless.
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)