[JBoss JIRA] Created: (TEIIDDES-971) In Designer, when importing tables with foreign keys, let user bring in tables without foreign key dependency errors / allow override
by Joel Tosi (JIRA)
In Designer, when importing tables with foreign keys, let user bring in tables without foreign key dependency errors / allow override
-------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-971
URL: https://issues.jboss.org/browse/TEIIDDES-971
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Affects Versions: 7.2
Environment: JBDS 4.0
Reporter: Joel Tosi
When mapping data in side Designer, a user is forced to bring in all dependencies (think tables with foreign key dependencies) in order to have a valid model. You should be able to override this - make the user aware of the missing data and allow user to accept the limitation.
Think of a scenario where there is a large database, with say 100 tables. Tons of foreign keys, etc. If a user wants to create a model against one table that has one foreign key (and bringing in its dependency brings another foreign key....etc) - if the user doesn't need the information from the related table for their modeling, then they should be allowed to override the warning and model without the dependency.
To reproduce - create a relational store and create 10 tables (A - J) - A has a foreign key to B, B to C, and so on. In designer, be able to override the warning when trying to model against just A.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (TEIIDDES-908) Replace Salesforce Extension Model created during import
by Barry LaFond (JIRA)
Replace Salesforce Extension Model created during import
---------------------------------------------------------
Key: TEIIDDES-908
URL: https://issues.jboss.org/browse/TEIIDDES-908
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Affects Versions: 7.3
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Blocker
Fix For: 7.4
In order to simplify JDBC import processing by replacing Designer's RelationalModelProcessor with Teiid's processor, the Salesforce Import use-case needs to be simplified by removing the need to have a separate Extension model.
TEIIDDES-905 is providing a new extension model framework that eliminates the need for a separate model.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (TEIIDDES-926) Create persistance and loading mechanism for XML-based Model Extension Definitions
by Barry LaFond (JIRA)
Create persistance and loading mechanism for XML-based Model Extension Definitions
----------------------------------------------------------------------------------
Key: TEIIDDES-926
URL: https://issues.jboss.org/browse/TEIIDDES-926
Project: Teiid Designer
Issue Type: Sub-task
Components: Import/Export, Modeling
Affects Versions: 7.4
Reporter: Barry LaFond
Assignee: Dan Florian
Priority: Blocker
Fix For: 7.4
Attachments: modelExtension.xsd, salesforce.mxd
The New Model Extension framework requires reading (loading) and writing XML-formatted Model Extension Definition properties.
These property definitions will replace the old "Extension Model" EMF construct.
Attached is a sample "salesforce.mxd" (Model eXtension Definition) file and a potential backing schema
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (TEIIDDES-714) Designer should clean up preview vdbs every time Teiid Server connection is made.
by Ramesh Reddy (JIRA)
Designer should clean up preview vdbs every time Teiid Server connection is made.
---------------------------------------------------------------------------------
Key: TEIIDDES-714
URL: https://jira.jboss.org/browse/TEIIDDES-714
Project: Teiid Designer
Issue Type: Bug
Components: Teiid Integration
Affects Versions: 7.1
Reporter: Ramesh Reddy
It is quite possible that that the preview vdbs deployed into a Teiid Server get out of sync with the Designer when the Server is restarted independent of the Designer. Since Designer keeps track of its preview vdbs based on workspace uuid, it is better that it cleans up its preview vdbs and data sources when the connection is made and connection is cleaned up. These actions may happen at both startup and shutdown of the Designer and also at the creation and discard of the Server settings once the Designer started. Otherwise there may be orphan VDBs left over in the Server.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months