December 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-109) Feature Request to add Model Project Templates

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-109?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-109: ---------------------------------- Fix Version/s: No Future (was: 8.1) > Feature Request to add Model Project Templates > ---------------------------------------------- > > Key: TEIIDDES-109 > URL: https://issues.jboss.org/browse/TEIIDDES-109 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration > Affects Versions: 6.0.0 > Reporter: Debbie Steigner > Assignee: Mark Drilling > Fix For: No Future > > > Please submit the creation and use of template projects as a feature. Template projects should work similiar to how templates work in IDE's. From Issue Tracker ticket https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1119) Need for global workspace location

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1119?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1119: ----------------------------------- Fix Version/s: Komodo (was: 8.1) > Need for global workspace location > ---------------------------------- > > Key: TEIIDDES-1119 > URL: https://issues.jboss.org/browse/TEIIDDES-1119 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: Komodo > > > With 7.6 Teiid Designer will be managing a new Model Extension framework which allows users to define Model Extension Definitions (MEDs) to inject additional properties into relational, web services, XML document and function models. > Initial design is to maintain a registry or both built-in and user-defined MED's within the user's workspace/.metadata/org.teiid.designer.extension folder. > Designer is also maintaining a similar Teiid Server registry in workspace/.metadata/org.teiid.designer.dqp > The "Import VDB" feature will probably need a place to store a registry of "Translator Overrides" so user can re-use these across VDB's rather than re-inputing these properties manually each time in their VDB editors. > The Data Tools Connection profile registry is also stored in a workspace/.metadata/org.eclipse.datatools.connectivity folder. Data Tool provides input/export features for persisting portions or all of the profile registry across workspace, but requires user to import/export each time. > Eclipse's ".metadata" folder concept is good from a single workspace standpoint, but these registries are: > 1) at risk of being deleted if workspace is cleared > 2) registry data (i.e. files) are not available/exposed for proper version control > So a solution might be to create the concept of a Global Workspace Location. This location would be set by the user if they choose. This location would contain folders for Teiid Server, Model Extension, Translator Overrides, Connection Profiles such that if a user changes workspaces they wouldn't necessarily have to re-import all of this data. > Maybe provide a "Global Workspace Explorer" view that would have some features/actions to do some appropriate management of the artifacts. > This would be a Usability -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1002) Designer requires a more flexible Model Object Refactoring framework to handle pre and post transaction events.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1002?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1002: ----------------------------------- Fix Version/s: No Future (was: 8.1) Komodo development will implement a refactor framework > Designer requires a more flexible Model Object Refactoring framework to handle pre and post transaction events. > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1002 > URL: https://issues.jboss.org/browse/TEIIDDES-1002 > Project: Teiid Designer > Issue Type: Task > Components: Modeling, Validation > Affects Versions: 7.5 > Reporter: Barry LaFond > Fix For: No Future > > > The current modeling/editing event and transaction framework in Designer cannot satisfy the requirements to perform certain cross-metamodel clean-up. > In particular, if a user Deletes a Scalar Function, the ObjectDeleteCommand results in the dependent resources (i.e. Virtual Tables and Procedures) being re-validated, which is good, but the UDFManager doesn't have a chance to de-register the affected Function model before revalidation. The resulting validation is incorrect. > Because ObjectDeleteCommand is in designer.core, there isn't any direct way that command could tell the UDFManager to perform the library clean-up. > So I propose an to expand the current "refactorModelHandler" extension point to handle this processing. > The current "RefactorModelExtensionManager" should be renamed to "RefactorModelManager" > Methods should be added such as: > preProcess(int type, Object[] objects) (Where type = DELETE, RENAME, MOVE, ADD) > postProcess(int type, Object[] objects) (Where type = DELETE, RENAME, MOVE, ADD) > Objects could be be Models, Files or EObjects -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-689) Needs to be some indication to user that a data source needs to be created

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-689?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-689. ----------------------------------- Assignee: Barry LaFond Resolution: Out of Date Designer 7.5/7.6 implemented an auto-deploy a Data Source if it doesn't exist upon Execute VDB action. So warning is not necessary. > Needs to be some indication to user that a data source needs to be created > -------------------------------------------------------------------------- > > Key: TEIIDDES-689 > URL: https://issues.jboss.org/browse/TEIIDDES-689 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration > Affects Versions: 7.1 > Reporter: John Verhaeg > Assignee: Barry LaFond > Fix For: 8.1 > > > After creating one or more models and putting them in a VDB, there is no indication that the user needs to have a corresponding data source available on the server before they can successfully deploy that VDB. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1273) XML File Importer Enhancements

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1273?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1273: -------------------------------------- Assignee: Barry LaFond > XML File Importer Enhancements > ------------------------------ > > Key: TEIIDDES-1273 > URL: https://issues.jboss.org/browse/TEIIDDES-1273 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 7.7 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 8.1 > > > There couple of suggestion I have to make XML/WSDL importers little more user friedly > - let the user double click on the element/attribute in the XML tree to add as column. Currently user need to right click and select to add. > - When a element/attribute is added have it decorated with some different graphic such that user knows that particular element/attribute is already added. (Elements can be added twice, there is no restrictions) > - Currently root element where the XPATH expressions for the columns are rooted from need to be selected by right clicking on the element. However the default shows empty. This should be by default set to "/", or have some mechanism to force this selection. Note also that if the user changes this after the column definitions, the original XPATH expressions need to be re-calculated to new root, or make the root read-only after the first selection. Another good guess for this is where the user first selected element from, set to that. > - may be a little text above the XML tree saying double click to select the columns would be helpful, I found right click by goofing around. > - I also believe "add" buttons not that useful, especially if they just adding a empty column and already have a "add selection as new column" button. Actually it is confusing. Keep up/down. "delete" is useful. You could also enable "delete" key on selection > - when same column is added, a different aliased name should be selected, as e1 as e1_1, e1_2 currently I see same name is given. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-307) Request ability to import Metadata via CWMI format

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-307?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-307: ---------------------------------- Fix Version/s: Future (was: 8.1) > Request ability to import Metadata via CWMI format > -------------------------------------------------- > > Key: TEIIDDES-307 > URL: https://issues.jboss.org/browse/TEIIDDES-307 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: Future > > > Per request for CWMI import capability into our repository. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-518) DTP context menu options on Teiid tables should consider whether virtual model supports update.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-518?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-518: ---------------------------------- Fix Version/s: Future (was: 8.1) > DTP context menu options on Teiid tables should consider whether virtual model supports update. > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-518 > URL: https://issues.jboss.org/browse/TEIIDDES-518 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.0 > Environment: Teiid Designer 7.0 + JBoss Dev Studio 3.0.1GA > Teiid 7.1 Alpha on EAP 5.1 > RHEL 6, OpenJDK 1.6 > Reporter: Ken Johnson > Fix For: Future > > > In DTP, Context menu for Table contains several options under Data->(Edit, Load, Extract, Sample Contents). For virtual tables, Extract and Sample Contents are fine. Edit and Load will attempt to write data. Thus a few issues: > a) These options should be disabled if the table in question does not have Supports Update checked. > b) These options should be tested when the table *does* have Update and Insert procedures defined. > c) Tables in SYS schema should never be writable. > When working with physical tables, all options should be available and work correctly. Cursory testing indicates this is the case - at least with a MySQL data source underlying the model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1402) Enable the diagram toolbar buttons, eg. Add Transformation Sources, by default

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1402?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1402: ----------------------------------- Fix Version/s: Future (was: 8.1) > Enable the diagram toolbar buttons, eg. Add Transformation Sources, by default > ------------------------------------------------------------------------------ > > Key: TEIIDDES-1402 > URL: https://issues.jboss.org/browse/TEIIDDES-1402 > Project: Teiid Designer > Issue Type: Sub-task > Components: Diagrams > Reporter: Paul Richardson > Assignee: Paul Richardson > Fix For: Future > > > At the moment, the toolbar diagram actions depend upon selection in the Model Explorer tree. > Better to enable the buttons by default. > If selection is made in Model Explorer tree then button uses that as before. If there is no selection then throw up wizard asking the user to select which models to add. So in the case of 'Add Transformation Source(s), all source and view model transformation diagrams nodes will be selectable. > Just helps the user avoid being confused as to why the buttons are disabled. Also helps with the view being the starting point for the use case. Maybe, consider New... buttons that would allow new sources to be created, ie. user starting from top-down approach with the view and working back to their sources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-714) Designer should clean up preview vdbs every time Teiid Server connection is made.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-714?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-714: ---------------------------------- Fix Version/s: Future (was: 8.1) > Designer should clean up preview vdbs every time Teiid Server connection is made. > --------------------------------------------------------------------------------- > > Key: TEIIDDES-714 > URL: https://issues.jboss.org/browse/TEIIDDES-714 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 7.1 > Reporter: Ramesh Reddy > Assignee: Dan Florian > Fix For: Future > > > 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. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-715) Oracle metadata import using Designer takes long time for large schemas

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-715?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-715: ---------------------------------- Fix Version/s: Future (was: 8.1) > Oracle metadata import using Designer takes long time for large schemas > ----------------------------------------------------------------------- > > Key: TEIIDDES-715 > URL: https://issues.jboss.org/browse/TEIIDDES-715 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1 > Reporter: Ramesh Reddy > Fix For: Future > > > Importing metadata from Oracle database seems to take longer than any other database, when the underlying the schema is large. This may be because the default settings with Oracle Driver tries to get lot more metadata then needed. Should explore ways to minimize the time to take import. > Teiid in the Dynamic VDB import uses "Table Types" and "schema" name to limit the number of tables it imports, may be we should adopt similar thing in Designer. It is possible that Designer is already doing such settings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2012