[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=13937601#comment-13937601 ] 

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

[~rareddy] Actually this requires all statements to be captured in a different way - every alter, drop, etc. to preserve the 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)