[teiid-issues] [JBoss JIRA] (TEIID-5211) Allow ability to forward-engineer into underlying data stores

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-5211:
-------------------------------------

Why does connection change? Curious to learn how you are using with Streaming sources?

Schema change in Teiid, either source or view model, does not make much difference the amount of work, I suspect handling source push down of the schema is more work as I was saying above. In either case, what Teiid lacking in that model is a repository for metadata and architecture differences with VDB artifact deployment model. Currently, metadata is refreshed at VDB deployment event, whereas with the other you need a central metadata repository where the VDB operates directly from and repository and can be dynamically updated.

> Allow ability to forward-engineer into underlying data stores
> -------------------------------------------------------------
>
>                 Key: TEIID-5211
>                 URL: https://issues.jboss.org/browse/TEIID-5211
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: Connector API
>            Reporter: Don Krapohl
>            Assignee: Steven Hawkins
>
> As a platform I am better able to better engineer my underlying data stores starting with a virtual model.
> Please add the ability to create, alter, and drop schema objects and relationahips (DDL) in underlying data sources.  Example, if I design a source in Teiid Designer I may wish to have Teiid do the DDL against the underlying data source(s).  This allows better abstraction an portability of the data model.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)