[teiid-issues] [JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594145#comment-13594145 ] 

Ramesh Reddy commented on TEIID-5285:
-------------------------------------

I am not sure if a new issue is warranted for this at least right now, but seems like these both issues go together. However, Schema Evolution seems to go much deeper. Schema Evolution, Data Redirection, and Data Migration all seem to integral parts of a solution. My ambitious goal is somehow to bring all together with some level of automation using Teiid, but right now I am really skimpy on details. Yes, I am trying to think through to put a proposal using FlywayDB for last day or so, but no luck yet.

I think we can tie FlywayDB's "migration" action to a new VDB version generation + deployment of that VDB + update of older VDB version (like an update of view transformation). But for needed code generation, the interception of migration script and native DB code generation is not clear without clear patterns of how to handle say "adding a new column",  "change data type" etc. 

> 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: Ramesh Reddy
>             Fix For: 11.x
>
>         Attachments: redirection-vdb.xml
>
>
> 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)