April 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1043) Test Connection on LDAP Connection Profile Wizard page does not enable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1043?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1043: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 780845|https://bugzilla.redhat.com/show_bug.cgi?id=780845] from MODIFIED to ON_QA > Test Connection on LDAP Connection Profile Wizard page does not enable > ---------------------------------------------------------------------- > > Key: TEIIDDES-1043 > URL: https://issues.jboss.org/browse/TEIIDDES-1043 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration > Affects Versions: 7.4, 7.5, 7.4.2 > Reporter: Barry LaFond > Assignee: Ted Jones > Fix For: 7.6 > > > Filling in required info in new LDAP connection profile does not enable the "Test Connection" button. > Looks like a "setPingButtonEnabled(true);" call needs to be made at the end of the LdapProfileDetailsWizardPage.validate() method, but adding the code ends up throwing an NPE when pressed. > So, it looks like there is no IConnectionFactoryProvider/IConnectionFactory contributed for the LDAP connection to use to "ping" the DB. This would have to be completed in order for the Test Connection button to not throw an NPE -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1291) Add "Deprecated" to the Function model class option in the New Model Wizard

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1291?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1291. ------------------------------------- Fix Version/s: (was: 7.7) Resolution: Done The display name needed to be changed in plugin.properties for the Function Metamodel to complete this issue. Also added a warning message in the NewModelWizard - informs to use relational procedures with function=true instead. Pull request - https://github.com/Teiid-Designer/teiid-designer/pull/144 > Add "Deprecated" to the Function model class option in the New Model Wizard > --------------------------------------------------------------------------- > > Key: TEIIDDES-1291 > URL: https://issues.jboss.org/browse/TEIIDDES-1291 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7 > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 8.1 > > > Function metamodel will be retired in 8.0 Designer > The New Model Wizard model class selector still says "Function". Add (Deprecated) to the label -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1691) Attempt to open 'Find Model Object' dialog results in NPE

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1691?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1691. ------------------------------------- Resolution: Done Added null check on the ok button to prevent NPE in ModelObjectSelectionDialog. Retested ok. Pull request - https://github.com/Teiid-Designer/teiid-designer/pull/144 > Attempt to open 'Find Model Object' dialog results in NPE > --------------------------------------------------------- > > Key: TEIIDDES-1691 > URL: https://issues.jboss.org/browse/TEIIDDES-1691 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.1 > > > Attempt to open the 'Find Model Object' dialog via 'Search > Teiid Designer > Find Model Object' results in this NPE: > java.lang.NullPointerException > at org.teiid.designer.ui.search.ModelObjectSelectionDialog.updateOkState(ModelObjectSelectionDialog.java:514) > at org.teiid.designer.ui.search.ModelObjectSelectionDialog.handleUpperSelectionChanged(ModelObjectSelectionDialog.java:416) > at org.teiid.designer.ui.search.ModelObjectSelectionDialog.handleSelectionChanged(ModelObjectSelectionDialog.java:400) > at org.eclipse.ui.dialogs.AbstractElementListSelectionDialog.handleWidgetSelected(AbstractElementListSelectionDialog.java:388) > at org.eclipse.ui.dialogs.AbstractElementListSelectionDialog.access$0(AbstractElementListSelectionDialog.java:383) > at org.eclipse.ui.dialogs.AbstractElementListSelectionDialog$1.widgetSelected(AbstractElementListSelectionDialog.java:373) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1291) Add "Deprecated" to the Function model class option in the New Model Wizard

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1291?page=com.atlassian.jira.plu... ] Mark Drilling updated TEIIDDES-1291: ------------------------------------ Fix Version/s: 8.1 > Add "Deprecated" to the Function model class option in the New Model Wizard > --------------------------------------------------------------------------- > > Key: TEIIDDES-1291 > URL: https://issues.jboss.org/browse/TEIIDDES-1291 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7 > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 7.7, 8.1 > > > Function metamodel will be retired in 8.0 Designer > The New Model Wizard model class selector still says "Function". Add (Deprecated) to the label -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1291) Add "Deprecated" to the Function model class option in the New Model Wizard

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1291?page=com.atlassian.jira.plu... ] Mark Drilling reopened TEIIDDES-1291: ------------------------------------- Assignee: Mark Drilling (was: Barry LaFond) Need to re-visit. In the Designer 8.1 Beta1 install, there is no (Deprecated) indication in the NewModel Wizard. > Add "Deprecated" to the Function model class option in the New Model Wizard > --------------------------------------------------------------------------- > > Key: TEIIDDES-1291 > URL: https://issues.jboss.org/browse/TEIIDDES-1291 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7 > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 7.7 > > > Function metamodel will be retired in 8.0 Designer > The New Model Wizard model class selector still says "Function". Add (Deprecated) to the label -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1691) Attempt to open 'Find Model Object' dialog results in NPE

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1691: --------------------------------------- Summary: Attempt to open 'Find Model Object' dialog results in NPE Key: TEIIDDES-1691 URL: https://issues.jboss.org/browse/TEIIDDES-1691 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 8.1 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 8.1 Attempt to open the 'Find Model Object' dialog via 'Search > Teiid Designer > Find Model Object' results in this NPE: java.lang.NullPointerException at org.teiid.designer.ui.search.ModelObjectSelectionDialog.updateOkState(ModelObjectSelectionDialog.java:514) at org.teiid.designer.ui.search.ModelObjectSelectionDialog.handleUpperSelectionChanged(ModelObjectSelectionDialog.java:416) at org.teiid.designer.ui.search.ModelObjectSelectionDialog.handleSelectionChanged(ModelObjectSelectionDialog.java:400) at org.eclipse.ui.dialogs.AbstractElementListSelectionDialog.handleWidgetSelected(AbstractElementListSelectionDialog.java:388) at org.eclipse.ui.dialogs.AbstractElementListSelectionDialog.access$0(AbstractElementListSelectionDialog.java:383) at org.eclipse.ui.dialogs.AbstractElementListSelectionDialog$1.widgetSelected(AbstractElementListSelectionDialog.java:373) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1149) Managing multiple versions of models

by Nelson Yap (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1149?page=com.atlassian.jira.plu... ] Nelson Yap commented on TEIIDDES-1149: -------------------------------------- As a client of red hat for EDS software, we are facing this issues not able to version the models via scm due to the fact that models can't be merge. I hope this will be resolved soon as it will make life much easier to have multiple developers working on the same models concurrently. > Managing multiple versions of models > ------------------------------------ > > Key: TEIIDDES-1149 > URL: https://issues.jboss.org/browse/TEIIDDES-1149 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration, Modeling > Affects Versions: 7.1.1, 7.4.2 > Reporter: Tom Fonteyne > Assignee: Barry LaFond > > We have a big requirement to more effectively manage multiple versions of models. In the future, we will have to maintain multiple versions of models and VDBs in order to guarantee compability for some clients while possibly providing new functionality for other clients using the same models. > We will also have "core models" (again possibly multiple releases) of business concepts which will be included in VDBs for specific clients and systems, then changes will need to be merged in from this one core set to many models/VDBs in the future. I posted a question to the SME list about this a few months ago ("Effectively version controlling models"). Ramesh provided some helpful ideas, such as stacking of VDBs, which we would prefer not to do because of foreseen management and performance (query planning) problems, and also how we can deploy multiple versions of the same VDB. > The problem remains however, that the only way we have at present to work with models is interactively through Teiid designer, and the only way to merge selectively (rather than replacing models) is manually. This process would potentially have to be repeated multiple times for each changeset. The customer is concerned that this approach will become unmanageable in the future. > Being able to merge through the designer would be great, but also non-interactively and automatable in some way too. Ideally, we would like to see a greater seperation of model management from the designer (in the same that it was done in a set of reusable classes which the designer makes use of also) so we have the option of using automatable tools (ie. maven) or building or own tools to do this merging. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1690) graphical visualization of explain plan

by Nelson Yap (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1690?page=com.atlassian.jira.plu... ] Nelson Yap updated TEIIDDES-1690: --------------------------------- Priority: Minor (was: Major) Description: It will be nice to have a visualization that display the execution plan in a graphical way. Makes understanding the plan much easier. > graphical visualization of explain plan > --------------------------------------- > > Key: TEIIDDES-1690 > URL: https://issues.jboss.org/browse/TEIIDDES-1690 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Nelson Yap > Priority: Minor > > It will be nice to have a visualization that display the execution plan in a graphical way. Makes understanding the plan much easier. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1690) graphical visualization of explain plan

by Nelson Yap (JIRA)

Nelson Yap created TEIIDDES-1690: ------------------------------------ Summary: graphical visualization of explain plan Key: TEIIDDES-1690 URL: https://issues.jboss.org/browse/TEIIDDES-1690 Project: Teiid Designer Issue Type: Feature Request Reporter: Nelson Yap -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1634) For Komodo, remove UUID from the persisted models, will help with ability to merge models

by Nelson Yap (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1634?page=com.atlassian.jira.plu... ] Nelson Yap commented on TEIIDDES-1634: -------------------------------------- This is a very useful feature.at the moment we are struggling to manage our models in a large development community across countries. The ability not able to merge models causing us not able to branch n merge into trunk for projects working on the same model that have different velocity if changes and release cycles. > For Komodo, remove UUID from the persisted models, will help with ability to merge models > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-1634 > URL: https://issues.jboss.org/browse/TEIIDDES-1634 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Van Halbert > Fix For: Komodo > > > When saving a model file, don't persist the UUID's in the file. This would make the file smaller and help with the user's ability to manage their models in a SCM and merge the changes. -- 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

12 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2013