[
https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-5285:
----------------------------------
Fix Version/s: 10.x
(was: 10.3)
Marking as stopped progress. I don't see this becoming a robust feature for 10.3.
We need to further clarify the usage scenarios:
Teiid Spring Boot
Teiid Side Car (do we have effective documentation for this?)
Let's also clarify what the configuration looks like - extension metadata on the
affected source tables, that can be enabled/disabled down to a table level (via env
variables or feature flags?). Are we attempting to hide / remove the source table?
There's not a great way to do that and still access it from the generated view /
triggers - unless we're considering data roles. Or a new metadata flag could be
needed, similar to hidden, that instead means "protected" (can only be accessed
from views/non-anon procedures).
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.x
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)