[teiid-issues] [JBoss JIRA] (TEIID-5867) Support capturing the IMPORT FORIGN DATA in DDLStringVisitor

[Steven Hawkins (Jira)]

    [ https://issues.redhat.com/browse/TEIID-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937587#comment-13937587 ] 

Steven Hawkins commented on TEIID-5867:
---------------------------------------

In general this does not map well to the logic in Teiid.  The statements are inherently serial - they take affect at the point in the ddl where they are defined.  Capturing them separately does not preserve the ordering.  It is also possible to have more than one import per schema.  

The only way to make this work would be to capture the import as a new record type and put it directly on the Schema so that it has a proper placement/resolving order.

> Support capturing the IMPORT FORIGN DATA in DDLStringVisitor
> ------------------------------------------------------------
>
>                 Key: TEIID-5867
>                 URL: https://issues.redhat.com/browse/TEIID-5867
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: Query Engine
>    Affects Versions: 13.0
>            Reporter: Ramesh Reddy
>            Assignee: Steven Hawkins
>            Priority: Major
>             Fix For: 13.1, 13.0.2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> In DatabaseStore logic the IMPORT FOREIGN DATA WRAPPER is treated as runtime statements that engine is processing at runtime vs build time representation of the VDB. It is a perfectly valid scenario.
> However, when working with VDB building, VDB-Import scenarios we need to capture these as is. can we provide a model in DatabaseStore to capture these in certain situations?



--
This message was sent by Atlassian Jira
(v7.13.8#713008)