[
https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin...
]
Steven Hawkins edited comment on TEIID-5285 at 4/12/18 3:55 PM:
----------------------------------------------------------------
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.
Are you thinking like a code generator approach? I had assumed that this would based upon
Spring Boot annotations and within the context of that vdb.
If we take the sidecar approach with this, which I think is
appropriate, as it will give a black box experience to the user
Our initial though was that since this makes the client dependent upon Teiid sql (and the
Teiid or pg client), it's not really something that can be too transparent. So the
initial target was just around Spring Boot integration.
As a black box / side car are you envisioning that Teiid is running on the same host and
you are deploying these kind of VDBs into it?
was (Author: shawkins):
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
Our initial though was that since this makes the client dependent upon Teiid sql (and the
Teiid or pg client), it's not really something that can be too transparent. So the
initial target was just around Spring Boot integration.
As a black box / side car are you envisioning that Teiid is running on the same host and
you are deploying these kind of VDBs into it?
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)