Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Done
Priority: Blocker
Fix Version/s: 8.2
Affects Version/s: 8.2
Component/s: Import/Export
Labels:
None

Current DdlImporter handles multiple DDL dialects, including the new Teiid-related modifications.

Refactor this class to allow dialect-specific implementations of an Interface that can be handed an AstNode and either process the node, or not.

Also need to allow for handing off Teiid-DDL Options to the Extension Assistants to inject the extension properties into the models. This is currently not handled correctly

is related to

TEIIDDES-883 Add support for Ingres database

Closed

TEIIDDES-904 Add JDBC import support for Intersystems Cache

Closed

TEIIDDES-930 Add Support for Mondrian (OLAP)

Closed

TEIIDDES-1193 Add Hive importer

Closed

TEIIDDES-1557 Add Greenplum importer

Closed

TEIIDDES-1674 DDL Importer - does not handle extension properties

Closed

TEIIDDES-1706 During DDL re-import the MergeProcessorImpl processes the ModelAnnotationImpl but misses key properties

Closed

TEIIDDES-1670 DDL Importer - problem with re-import when setting descriptions

Closed

TEIIDDES-1705 Model imported from DDL is missing relational model extension MED

Closed

TEIIDDES-1176 Usability Issue: On DDL importer, need better feed back when a file cannot be imported

Closed

TEIIDDES-1655 Teiid importer needs to handle schema and catalog cases for generated model

Closed

TEIIDDES-1725 As default behavior, Importing DDL into an existing model removed the other tables

Closed

TEIIDDES-1654 DDL Importer needs to better handle constraint naming in generated model

Closed

(8 is related to)

Assignee:: Paul Richardson

Reporter:: Barry LaFond

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2013/05/23 3:43 PM

Updated:: 2013/12/09 9:34 AM

Resolved:: 2013/06/11 10:35 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates