April 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2134) Changing connection profile of a source model does not update the translator in importing VDB

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2134?page=com.atlassian.jira.plu... ] Lucie Fabrikova commented on TEIIDDES-2134: ------------------------------------------- In the VdbModelEntry.synchronizeModelEntry( final IProgressMonitor monitor ), there is if-condition which is evaluated to true only if the translator cell in vdb editor (Source binding tab, Translator name) is empty: [672] if (ModelUtil.isPhysical(model)) { ... [677] String translatorName = this.sourceInfo.getSource(0).getTranslatorName(); if (CoreStringUtil.isEmpty(translatorName){ ... //if I understand correctly, the translator is set for the model entry here } Proposed fix for the translator: - evaluate the helper.getTranslatorName(mr) -- if it is not null and not empty, then perform the body of if-condition too > Changing connection profile of a source model does not update the translator in importing VDB > --------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2134 > URL: https://issues.jboss.org/browse/TEIIDDES-2134 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3 > Reporter: Andrej Šmigala > > Steps to reproduce: > # Import a source model > # Create a new VDB and add the source model to it > # Set connection profile to a different db (with different translator) > # Synchronize the model in the VDB > The translator and JNDI name are not updated in the 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2135) Parse Error Persists After Correcting Query

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-2135: ----------------------------------- Summary: Parse Error Persists After Correcting Query Key: TEIIDDES-2135 URL: https://issues.jboss.org/browse/TEIIDDES-2135 Project: Teiid Designer Issue Type: Feature Request Components: Validation Affects Versions: 8.5 Reporter: Ted Jones Assignee: Barry LaFond Fix For: 8.5 After incurring a parse error in the sql transformation error, the parse error remains even after correcting the sql. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2134) Changing connection profile of a source model does not update the translator in importing VDB

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2134: ---------------------------------------- Summary: Changing connection profile of a source model does not update the translator in importing VDB Key: TEIIDDES-2134 URL: https://issues.jboss.org/browse/TEIIDDES-2134 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 8.3 Reporter: Andrej Šmigala Steps to reproduce: # Import a source model # Create a new VDB and add the source model to it # Set connection profile to a different db (with different translator) # Synchronize the model in the VDB The translator and JNDI name are not updated in the 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2133) Query Parsing Error Missing Parameter

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-2133: ----------------------------------- Summary: Query Parsing Error Missing Parameter Key: TEIIDDES-2133 URL: https://issues.jboss.org/browse/TEIIDDES-2133 Project: Teiid Designer Issue Type: Bug Components: Validation Affects Versions: 8.5 Reporter: Ted Jones Assignee: Barry LaFond Fix For: 8.5 When entering an invalid query in the transformation editor, the error message is missing the Teiid version parameter: "The query is not parsable. Error in parsing of sql - The given sql syntax is not supported by the Teiid client version {1}" -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1998) Connection Profile loses Binding Type

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1998?page=com.atlassian.jira.plu... ] Ted Jones reopened TEIIDDES-1998: --------------------------------- Seeing this again running from master. > Connection Profile loses Binding Type > ------------------------------------- > > Key: TEIIDDES-1998 > URL: https://issues.jboss.org/browse/TEIIDDES-1998 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3 > Reporter: Ted Jones > Assignee: Barry LaFond > Fix For: 8.3.1 > > > Whenever importing WSDL into Source model, the connection profile loses it's binding info and I am required to edit the CP and add the binding info with each import. We should find a way to persist it or some other way to get the binding for import. > The error is: "Connection Profile is invalid since it does not contain the required property DefaultBinding". -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2132) issues with MED editor

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2132?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2132. ------------------------------------ Resolution: Done fixed > issues with MED editor > ---------------------- > > Key: TEIIDDES-2132 > URL: https://issues.jboss.org/browse/TEIIDDES-2132 > Project: Teiid Designer > Issue Type: Bug > Components: Editors, Extension Framework > Affects Versions: 8.4, 8.3.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.5 > > > 1) When setting initial value for property and error is produced, then when the error is fixed (setting to an actual allowed value) the error messages at top of dialog remains. > 2) When creating new Display name or Description.... > - Entering Eng (with keystrokes) and hitting Enter, then Tab to text box.... > - Enter some text and error says local has not been set -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2132) issues with MED editor

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2132: -------------------------------------- Summary: issues with MED editor Key: TEIIDDES-2132 URL: https://issues.jboss.org/browse/TEIIDDES-2132 Project: Teiid Designer Issue Type: Bug Components: Editors, Extension Framework Affects Versions: 8.4, 8.3.2 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 8.5 1) When setting initial value for property and error is produced, then when the error is fixed (setting to an actual allowed value) the error messages at top of dialog remains. 2) When creating new Display name or Description.... - Entering Eng (with keystrokes) and hitting Enter, then Tab to text box.... - Enter some text and error says local has not been set -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2094) Support for dynamic extension metadata

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2094?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2094: ---------------------------------------- >> We'll create a MED file (if not already registered) for the Translator during Teiid Connection Import * MED will contain a new string attribute which holds the server version as the origin/version of the extension properties * MED will contain a new boolean attribute representing a "built-in-translator" state. This will enable Designer to "lock" the MED during import and prevent accidental modification. Maybe it's permanent and users will need to "clone" the MED in order to make a copy and modify it's properties * User will not be able to edit any imported extension properties (unless they create/clone this special MED and re-apply to model) >> (OPTION) User will have to option during import to NOT save this MED in their registry. * The OPTIONS properties and MED structure will be injected into model * These extension properties will not be visible via the properties view because there will not be a registered MED > Support for dynamic extension metadata > --------------------------------------- > > Key: TEIIDDES-2094 > URL: https://issues.jboss.org/browse/TEIIDDES-2094 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Paul Richardson > Priority: Critical > > Currently when Teiid core implements a new translator or customer/user implements a custom translator that has extension metadata, before they can use the translator in Designer to do some modeling, they need to define MED and register it. > With completion of TEIID-2904, in Teiid 8.7, a Admin api method can be used to interrogate the extension metadata properties defined for a translator. > Currently if user uses Teiid Connection importer with any new translator, it ignores all the extension metadata properties and removes them from the returned DDL that Designer did not recognize. That is really bad for custom connectors, because the VDB will not work properly once it is deployed back to Teiid Server. > I propose to devise a way to generate a dynamic MED for the purposes of current metadata import of the source and use it during the import and not ignore those extension metadata properties. > Depending upon implementation detail, we can also read the translators and their extension metadata support during the initial connection time and create all the required MEDs and register them. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2131) With Teiid Designer, user can't set "System Table Access" for "VDB Data Role" with a small display

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-2131: ------------------------------------- Summary: With Teiid Designer, user can't set "System Table Access" for "VDB Data Role" with a small display Key: TEIIDDES-2131 URL: https://issues.jboss.org/browse/TEIIDDES-2131 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 8.3.1 Reporter: Van Halbert Assignee: Barry LaFond Description of problem: With Teiid Desitner, user can't set "System Table Access" for "VDB Data Role" with a small display Version-Release number of selected component (if applicable): Teiid Designer：7.7.5.v20140302-1621-H4-Final Steps to Reproduce: 1. Set display resolution as "1024×768" 2. Open VDB file 3. Click "add data role" button Actual results: User can't set a check box for "System Tables Access" Expected results: ModalPanel has a scroll window, so user can set it -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2131) With Teiid Designer, user can't set "System Table Access" for "VDB Data Role" with a small display

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2131?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2131: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1091854 > With Teiid Designer, user can't set "System Table Access" for "VDB Data Role" with a small display > ---------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2131 > URL: https://issues.jboss.org/browse/TEIIDDES-2131 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 8.3.1 > Reporter: Van Halbert > Assignee: Barry LaFond > > Description of problem: > With Teiid Desitner, user can't set "System Table Access" for "VDB Data Role" with a small display > Version-Release number of selected component (if applicable): > Teiid Designer：7.7.5.v20140302-1621-H4-Final > Steps to Reproduce: > 1. Set display resolution as "1024×768" > 2. Open VDB file > 3. Click "add data role" button > Actual results: > User can't set a check box for "System Tables Access" > Expected results: > ModalPanel has a scroll window, so user can set it -- 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

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2014