[JBoss JIRA] Created: (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard
by Paul Nittel (JIRA)
Data types inported from flat file partially implemented in wizard
------------------------------------------------------------------
Key: TEIIDDES-1037
URL: https://issues.jboss.org/browse/TEIIDDES-1037
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.5
Reporter: Paul Nittel
The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement.
I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing.
Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point.
The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (TEIIDDES-1197) Create Runtime Artifacts Configuration View or Editor
by Barry LaFond (Created) (JIRA)
Create Runtime Artifacts Configuration View or Editor
-----------------------------------------------------
Key: TEIIDDES-1197
URL: https://issues.jboss.org/browse/TEIIDDES-1197
Project: Teiid Designer
Issue Type: Sub-task
Affects Versions: 7.6
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.7
Teiid Designer has a number of views, editors that allow management of various values, artifacts or properties of artifacts.
This info includes:
- Data Tools Project Connection Profiles
- Teiid Data Sources and Translators
- Translator Overrides (currently only in VDBs)
- Re-usable Model Extension Definitions (MEDs)
- VDB's
Single view/editor containing the status of these items for a given workspace would help clarify what a user is working with and also better enable re-use across local projects
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (TEIIDDES-1079) Create Import VDB wizard
by Barry LaFond (JIRA)
Create Import VDB wizard
------------------------
Key: TEIIDDES-1079
URL: https://issues.jboss.org/browse/TEIIDDES-1079
Project: Teiid Designer
Issue Type: Feature Request
Components: Editors, Modeling, VDB & Execution
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Critical
Fix For: 7.6
For usability improvements and migration support, it would be great to be able to import a VDB into a workspace, extract the models from the VDB into a new project (along with the VDB) and allow the user to begin to start editing the models as if they were new.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (TEIIDDES-1195) Enable the coping of translator overrides for use in other VDB's with same translator
by Van Halbert (Created) (JIRA)
Enable the coping of translator overrides for use in other VDB's with same translator
-------------------------------------------------------------------------------------
Key: TEIIDDES-1195
URL: https://issues.jboss.org/browse/TEIIDDES-1195
Project: Teiid Designer
Issue Type: Sub-task
Components: VDB & Execution
Affects Versions: 7.4.2
Reporter: Van Halbert
Assignee: Dan Florian
Fix For: 7.7
Building multiple vdb's in a single project, so that each will have different overrides to the translator in order to test various conditions. However, the translator override that is created for each vdb is called the same name (i.e,. <translator_name>-1), giving an illusion that properties maybe shared between the two. Unfortunately, was unable to change the name of the translator override so that each vdb override was specific.
VDB's need to be more "transportable", so being able to extract Translator properties and share them/apply them across VDB's seems a must.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (TEIIDDES-1153) Create Model Extension Definition (MED) Compare Editor
by Dan Florian (Created) (JIRA)
Create Model Extension Definition (MED) Compare Editor
------------------------------------------------------
Key: TEIIDDES-1153
URL: https://issues.jboss.org/browse/TEIIDDES-1153
Project: Teiid Designer
Issue Type: Enhancement
Components: Editors
Affects Versions: 7.6
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 7.7
It is important for a user to know the differences between a MED in the registry and the same MED in the workspace. The MED in the workspace may have changes and the user should be able to see those differences. The compare editor should also be able to compare MEDs that are both in the workspace. When comparing with a registry MED, the registry MED is readonly and cannot be changed by the compare editor. Eclipse has a compare editor framework that should be used. One approach would be to use the built-in text compare editor but having a GUI compare editor might be nicer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years