September 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-606) Criteria and Expression builder actions on Transformation Editor not enabling or not launching with editable values

by Barry LaFond (JIRA)

Criteria and Expression builder actions on Transformation Editor not enabling or not launching with editable values -------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-606 URL: https://jira.jboss.org/browse/TEIIDDES-606 Project: Teiid Designer Issue Type: Bug Components: Editors, Transformations Affects Versions: 7.1 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.1.1 After creating simple SELECT * FROM and adding a WHERE clause, tried to set cursor in "Where" clause and EDIT the clause and did not work. Same after creating an expression in the "SELECT" segment. Setting cursor in the new expression (i.e. concat(aaa, bbb) as ccc) does not enable launch expression builder button. Due to refactoring of Display Node logic (TEIIDDES-567), the DisplayNode tree structure has changed and existing enablement checks and cursor position checks need to be rewritten. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-256) Teiid is making column names upper case, even when specified as lower

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-256?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDDES-256: ----------------------------------------- this shouldn't be happening any more, it also shouldn't be marked as major since the query is valid either way. > Teiid is making column names upper case, even when specified as lower > --------------------------------------------------------------------- > > Key: TEIIDDES-256 > URL: https://jira.jboss.org/browse/TEIIDDES-256 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 6.2.0 > Environment: Fedora 12, OpenJDK Server VM (build 14.0-b16, mixed mode), Teiid build 1/19/2010 > Reporter: Paul Nittel > Attachments: TextMetadataTesting.zip > > > I've got a transformation that defines two columns like this: > SELECT > c_count, COUNT(*) AS custdist > FROM > (SELECT C_CUSTKEY, COUNT(O_ORDERKEY) AS c_count FROM TPCR.CUSTOMER LEFT OUTER JOIN TPCR.ORDERS ON C_CUSTKEY = O_CUSTKEY AND O_COMMENT NOT LIKE '%special%requests%' GROUP BY C_CUSTKEY) AS c_orders > GROUP BY c_count > In the past, when queried (SELECT * FROM ...), the columns were spelled c_count and custdist. Now they're spelled C_COUNT and custdist. Do we now upcase column names that are not specified as an alias (or do we only preserve case on aliases)? > I noticed this in AdminShell, but see the Designer is also doing it, so I'm thinking it's the query engine, not the tool. (Steve H. agreed it should still be lower case when queried.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-589) Incorrect alias resolving upon validation with self-joined queries in Transformation Editor

by Carmon Hesse (JIRA)

Incorrect alias resolving upon validation with self-joined queries in Transformation Editor ------------------------------------------------------------------------------------------- Key: TEIIDDES-589 URL: https://jira.jboss.org/browse/TEIIDDES-589 Project: Teiid Designer Issue Type: Bug Components: Transformations, Validation Affects Versions: 7.1 Reporter: Carmon Hesse Upon Save/Validate of the following SQL query, the self-joined query transforms the alias.column in the WHERE clause into alias.view.model.table.column. This also occurs using the full-path to adress two tables with the same name from two different sources. Only the aliases in the WHERE clause are affected by this problem. SELECT p1.name, p1.version FROM view.model.table p1, view.model.table.p2 WHERE p1.id = p2.id AND p1.name = p2.name into SELECT p1.name, p1.version FROM view.model.table p1, view.model.table.p2 WHERE p1.view.model.table.id = p2.view.model.table.id AND p1.view.model.table.name = p2.view.model.table.name Error message is: The query is parsable but not resolvable. Resolver Error: Symbol p1.view.model.table.id is specified with an unknown group context -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-608) Able to begin to create a subtype using Read Only XSD, but get error about read-only cannot be modified

by Paul Nittel (JIRA)

Able to begin to create a subtype using Read Only XSD, but get error about read-only cannot be modified ------------------------------------------------------------------------------------------------------- Key: TEIIDDES-608 URL: https://jira.jboss.org/browse/TEIIDDES-608 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.1 Reporter: Paul Nittel Fix For: 7.1.1 Section 1.3 of the E2E Simple Datatypes Editor Test script specifies attempts at changing a Read-Only XSD file. All actions and links should be disabled, but I found the "Create subtype of this datatype..." link was enabled. I clicked it and entered a name for the subtype. When I clicked OK button, I got an error indicating the XSD file coud not be modified. The Create link should be disabled when the model is Read-Only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-611) NPE when executing Designer with Simple Datatypes Editor open

by Paul Nittel (JIRA)

NPE when executing Designer with Simple Datatypes Editor open ------------------------------------------------------------- Key: TEIIDDES-611 URL: https://jira.jboss.org/browse/TEIIDDES-611 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.1 Environment: JBDS 3.0.1, Teiid Designer 7.1 Reporter: Paul Nittel Fix For: 7.1.1 I have found that if the Designer is closed with the Simple Datatypes Editor open, I receive a NPE when I restart the Designer. Error 2010-09-14 12:57:02.698 Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench". java.lang.NullPointerException at com.metamatrix.ui.AbstractUiPlugin.getActionService(AbstractUiPlugin.java:157) at com.metamatrix.modeler.internal.ui.editors.ModelEditorActionContributor.setActivePage(ModelEditorActionContributor.java:213) at com.metamatrix.modeler.internal.ui.editors.ModelEditorActionContributor.setActiveEditor(ModelEditorActionContributor.java:156) at org.eclipse.ui.internal.EditorActionBars.partChanged(EditorActionBars.java:342) at org.eclipse.ui.internal.WorkbenchPage$3.run(WorkbenchPage.java:632) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.WorkbenchPage.activatePart(WorkbenchPage.java:621) at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3527) at org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:614) at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:956) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$28.runWithException(Workbench.java:1384) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2316) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-613) Default War File Generation Location Incorrect

by Ted Jones (JIRA)

Default War File Generation Location Incorrect ---------------------------------------------- Key: TEIIDDES-613 URL: https://jira.jboss.org/browse/TEIIDDES-613 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.1 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.1.1 The slashes in the default war file location are backward slashes instead of forward slashes on Linux which causes a folder to be created instead of a path. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-612) Creating subtype from Boolean built-in type fails (Unhandled event loop exception)

by Paul Nittel (JIRA)

Creating subtype from Boolean built-in type fails (Unhandled event loop exception) ---------------------------------------------------------------------------------- Key: TEIIDDES-612 URL: https://jira.jboss.org/browse/TEIIDDES-612 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.1 Environment: JBDS 3.0.1, Teiid Designer 7.1 Reporter: Paul Nittel Fix For: 7.1.1 In the E2E Simple Datatypes Editor test script, section 2.1, the script calls for creating a subtype of the Boolean built-in type. When I click the link to create the subtype, the Designer indicates it's working. After a period of time, when nothing has happened, clicking again produced this exception: Error 2010-09-14 13:09:56.813 Unhandled event loop exception java.lang.NullPointerException at java.io.File.<init>(File.java:222) at com.metamatrix.modeler.internal.ui.forms.HyperlinkComponentSet.valueClicked(HyperlinkComponentSet.java:46) at com.metamatrix.modeler.internal.ui.forms.HyperlinkComponentSet$1.valueClicked(HyperlinkComponentSet.java:84) at com.metamatrix.modeler.internal.ui.forms.FormTextObjectEditor$MyHyperlinkListener.linkActivated(FormTextObjectEditor.java:162) at org.eclipse.ui.forms.widgets.FormText.activateLink(FormText.java:1548) at org.eclipse.ui.forms.widgets.FormText.handleMouseClick(FormText.java:1351) at org.eclipse.ui.forms.widgets.FormText.access$16(FormText.java:1323) at org.eclipse.ui.forms.widgets.FormText$6.mouseUp(FormText.java:448) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:207) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-607) Need a "Set Translator Name" action to allow using custom translators with Preview Data action.

by Barry LaFond (JIRA)

Need a "Set Translator Name" action to allow using custom translators with Preview Data action. ----------------------------------------------------------------------------------------------- Key: TEIIDDES-607 URL: https://jira.jboss.org/browse/TEIIDDES-607 Project: Teiid Designer Issue Type: Feature Request Affects Versions: 7.1 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 7.1.1 Custom translators cannot be tested in Designer using Preview Data action. This is because the Translator name is "discovered" and set at import time or via "Set Connection Profile" action. By providing a "Modeling > Set Translator Name" action, users can change the translator name prior to executing Preview Data.bb -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-525) In Import wizards, add ability to launch Connection Profile property editor (so I can easily fix bad connection props).

by Ken Johnson (JIRA)

In Import wizards, add ability to launch Connection Profile property editor (so I can easily fix bad connection props). ----------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-525 URL: https://jira.jboss.org/browse/TEIIDDES-525 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.0 Environment: Teiid Designer 7, Helios, RHEL 6, OpenJDK 6 Reporter: Ken Johnson When importing (e.g. Metadata from JDBC Database), I can choose an existing connection profile or create a new one. If the one I create or choose has an error - say a bad password, to fix it I have to: 1. cancel out of the import wizard 2. switch perspectives to DTP 3. edit the properties for the offending connection profile 4. switch perspective back to Designer 5. re-run import wizard to try again. Since connection property errors are a common occurrence, this is a usability issue. Suggest adding the ability to launch the connection profile property editor directly from the import wizard so the correction can be made, saved, and retested without the context switches. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-567) Refactor display node logic

by Steve Hawkins (JIRA)

Refactor display node logic --------------------------- Key: TEIIDDES-567 URL: https://jira.jboss.org/browse/TEIIDDES-567 Project: Teiid Designer Issue Type: Quality Risk Components: Editors, Teiid Integration Affects Versions: 7.1 Reporter: Steve Hawkins DisplayNode logic duplicates Teiid SQLStringVisitor logic and quickly gets out of synch. There are also several pending changes (nested table syntax, named parameter syntax) that could have their fixes obviated by just changing the display node logic to use the SQLStringVisitor to construct the display node tree. The bulk of the display node classes can be removed since they contain no logic and could be replaced with instanceof checks on the underlying language object instead. Teiid's SQLStringVisitor will need some modifications to accommodate this change, which will get rolled into 7.1.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2010