August 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Closed: (TEIID-1200) Non-parsable SQL in transformation provides no help to user - NPE in stack trace

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1200?page=com.atlassian.jira.plugin.s... ] Steve Hawkins closed TEIID-1200. -------------------------------- > Non-parsable SQL in transformation provides no help to user - NPE in stack trace > -------------------------------------------------------------------------------- > > Key: TEIID-1200 > URL: https://jira.jboss.org/browse/TEIID-1200 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.0 > Environment: Fedora 12, OpenJDK, Designer 6/28 > Reporter: Paul Nittel > Assignee: Steve Hawkins > Fix For: 7.1 > > Attachments: E2eUpdateVirtualGroupsTestScript.odt, UpdatesProject.zip > > > Neither the error nor the stack trace provides the user with any assistance in correcting their SQL error. (BTW, in MMx 554, this parsed.) > While attempting the Update Virtual Groups modeling, I ran into this problem defining the Update procedure for UpdateProduct. After pasting in the SQL text, I validated the SQL and received: > The query is not parsable. > Error encountered while validating the transformation. > The message log shows: > Error 2010-06-30 11:32:04.784 Error encountered while validating the transformation. > Please check the Message log for exceptions > java.lang.NullPointerException > at org.teiid.query.validator.ValidationVisitor.validateTranslateCriteria(ValidationVisitor.java:536) > at org.teiid.query.validator.ValidationVisitor.visit(ValidationVisitor.java:479) > at org.teiid.query.sql.proc.TranslateCriteria.acceptVisitor(TranslateCriteria.java:134) > at org.teiid.query.sql.navigator.AbstractNavigator.visitVisitor(AbstractNavigator.java:53) > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.preVisitVisitor(PreOrPostOrderNavigator.java:125) > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:461) > at org.teiid.query.sql.proc.TranslateCriteria.acceptVisitor(TranslateCriteria.java:134) > at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:62) > at org.teiid.query.validator.Validator$1.visitNode(Validator.java:88) > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:475) > at org.teiid.query.sql.lang.Update.acceptVisitor(Update.java:157) > at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:62) > at org.teiid.query.validator.Validator$1.visitNode(Validator.java:88) > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:158) > at org.teiid.query.sql.proc.AssignmentStatement.acceptVisitor(AssignmentStatement.java:133) > at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:62) > at org.teiid.query.validator.Validator$1.visitNode(Validator.java:88) > at org.teiid.query.sql.navigator.AbstractNavigator.visitNodes(AbstractNavigator.java:73) > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:175) > at org.teiid.query.sql.proc.Block.acceptVisitor(Block.java:88) > at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:62) > at org.teiid.query.validator.Validator$1.visitNode(Validator.java:88) > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:289) > at org.teiid.query.sql.proc.IfStatement.acceptVisitor(IfStatement.java:147) > at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:62) > at org.teiid.query.validator.Validator$1.visitNode(Validator.java:88) > at org.teiid.query.sql.navigator.AbstractNavigator.visitNodes(AbstractNavigator.java:73) > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:175) > at org.teiid.query.sql.proc.Block.acceptVisitor(Block.java:88) > at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:62) > at org.teiid.query.validator.Validator$1.visitNode(Validator.java:88) > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:218) > at org.teiid.query.sql.proc.CreateUpdateProcedureCommand.acceptVisitor(CreateUpdateProcedureCommand.java:144) > at org.teiid.query.validator.Validator.executeValidation(Validator.java:93) > at org.teiid.query.validator.Validator.validate(Validator.java:55) > at org.teiid.query.validator.Validator.validate(Validator.java:41) > at com.metamatrix.modeler.transformation.validation.TransformationValidator.validateCommand(TransformationValidator.java:389) > at com.metamatrix.modeler.transformation.validation.TransformationValidator.validateSql(TransformationValidator.java:297) > at com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent.validateSql(QueryDisplayComponent.java:263) > at com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent.setText(QueryDisplayComponent.java:178) > at com.metamatrix.query.ui.sqleditor.SqlEditorPanel.setTextInTransaction(SqlEditorPanel.java:421) > at com.metamatrix.query.ui.sqleditor.SqlEditorPanel$4.run(SqlEditorPanel.java:464) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) > at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) > at com.metamatrix.query.ui.sqleditor.SqlEditorPanel.setText(SqlEditorPanel.java:470) > at com.metamatrix.query.ui.sqleditor.SqlEditorPanel.setText(SqlEditorPanel.java:495) > at com.metamatrix.query.ui.sqleditor.SqlEditorPanel.validate(SqlEditorPanel.java:526) > at com.metamatrix.query.ui.sqleditor.SqlEditorPanelWrapper.validate(SqlEditorPanelWrapper.java:138) > at com.metamatrix.query.internal.ui.sqleditor.actions.Validate.doRun(Validate.java:52) > at com.metamatrix.ui.actions.AbstractAction$1.run(AbstractAction.java:537) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at com.metamatrix.ui.actions.AbstractAction.run(AbstractAction.java:540) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452) > 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:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1175) SqlServer 2005 - Queries failing due to negative values being treated as positive values

by Warren Gibson (JIRA)

SqlServer 2005 - Queries failing due to negative values being treated as positive values ---------------------------------------------------------------------------------------- Key: TEIID-1175 URL: https://jira.jboss.org/browse/TEIID-1175 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Warren Gibson Assignee: Steve Hawkins It appears results are being returned without consideration for the negative(-) sign - RDBMS_Test_Queries_1000_TestQuery169 SELECT SmallA.IntKey FROM SmallA WHERE SmallA.StringNum > 11 AND SmallA.StringNum < 15 ORDER BY IntKey Query suite is expecting 3 rows returned. Query results straight to source returns: 36 37 38 Query results from Teiid: 10 11 12 13 36 37 38 Source contains the following for IntKey and StringNum IntKey StringNum 0 -24 1 <null> 2 -22 3 -21 4 -20 5 -19 6 -18 7 -17 8 -16 9 -15 10 -14 11 -13 12 -12 13 -11 14 -10 15 -9 16 -8 17 <null> 18 -6 19 -5 20 -4 21 -3 22 -2 23 -1 24 0 25 1 26 2 27 3 28 4 29 5 30 6 31 7 32 8 33 <null> 34 10 35 11 36 12 37 13 38 14 39 15 40 16 41 17 42 18 43 19 44 20 45 21 46 22 47 23 48 24 -- 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

14 years, 4 months

2
10
0 / 0

[JBoss JIRA] Created: (TEIID-1203) "connector-ws" is not visible as one of the avaialble connectors

by Ramesh Reddy (JIRA)

"connector-ws" is not visible as one of the avaialble connectors ---------------------------------------------------------------- Key: TEIID-1203 URL: https://jira.jboss.org/browse/TEIID-1203 Project: Teiid Issue Type: Bug Components: Misc. Connectors Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1 When queries through admin api for available data source templates getDataSourceTemplateNames(); ===> [connector-file, connector-jdbc-xa, connector-ldap, connector-salesforce, connector-jdbc] no "connector-ws" -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Closed: (TEIID-1192) JDBC driver doesn't accept underscores _ in server names

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1192?page=com.atlassian.jira.plugin.s... ] Steve Hawkins closed TEIID-1192. -------------------------------- > JDBC driver doesn't accept underscores _ in server names > -------------------------------------------------------- > > Key: TEIID-1192 > URL: https://jira.jboss.org/browse/TEIID-1192 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 7.0 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 7.1 > > > DBC driver does not support underscored in the server name. So > jdbc:metamatrix:FederatedSearch_VDB@mm://127.0.0.1:31000;version=2 will work but its names counterpart > jdbc:metamatrix:FederatedSearch_VDB@mm://sup_mm:31000;version=2 does not will not. -- 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1181) Teiid Pushdown queries producing unexpected results (Sybase 12.5)

by Warren Gibson (JIRA)

Teiid Pushdown queries producing unexpected results (Sybase 12.5) ----------------------------------------------------------------- Key: TEIID-1181 URL: https://jira.jboss.org/browse/TEIID-1181 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Environment: Teiid 7.1 Reporter: Warren Gibson Assignee: Steve Hawkins The attached sampling of 43 queries submitted against Sybase 12.5 are producing unexpected results in Teiid pushdown query testing but are producing expected results when submitted straight to the source through Squirrel. Column A of the attached spreadsheet contains the query and my comments. Columns B & C contains info from the query testing run. I am attaching the VDB, ds, and driver. If I can provide any additional information please let me know. -- 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

14 years, 4 months

2
9
0 / 0

[JBoss JIRA] Created: (TEIID-1167) Add support for primary key handling in temp tables

by Steve Hawkins (JIRA)

Add support for primary key handling in temp tables --------------------------------------------------- Key: TEIID-1167 URL: https://jira.jboss.org/browse/TEIID-1167 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 We should add support for primary keys in our temp tables. With indexing, this support will also be used as the basis for our intermediate view level caching. -- 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

14 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-1173) Provide a facility to create "empty" VDBs for preview purpose

by Ramesh Reddy (JIRA)

Provide a facility to create "empty" VDBs for preview purpose ------------------------------------------------------------- Key: TEIID-1173 URL: https://jira.jboss.org/browse/TEIID-1173 Project: Teiid Issue Type: Task Components: Server Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1 For supporting the preview functionality, Designer team requests to be able to deploy a VDB with no models in them, so that required models can be merged into it later on. However currently this fails because, Teiid VDB deployer check to make sure there is a model and it has metadata. This restriction needs to be relaxed for preview VDBs. -- 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

14 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1153) Turned of ProfileService authenticatiion and it caused an NPE in the Teiid RHQ Plugin

by Van Halbert (JIRA)

Turned of ProfileService authenticatiion and it caused an NPE in the Teiid RHQ Plugin ------------------------------------------------------------------------------------- Key: TEIID-1153 URL: https://jira.jboss.org/browse/TEIID-1153 Project: Teiid Issue Type: Bug Components: Jopr Plugin Environment: SOA-P Reporter: Van Halbert Assignee: Steve Hawkins Turned of ProfileService authenticatiion and it caused an NPE in the Teiid RHQ Plugin, Exception: java.lang.Exception: Discovery component invocation failed. at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:270) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:637) Caused by: java.lang.NullPointerException at org.teiid.rhq.plugin.util.ProfileServiceUtil.getSimpleValue(ProfileServiceUtil.java:296) at org.teiid.rhq.plugin.PlatformDiscoveryComponent.discoverResources(PlatformDiscoveryComponent.java:66) at sun.reflect.GeneratedMethodAccessor339.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:266) ... 5 more -- 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

14 years, 4 months

3
3
0 / 0

[JBoss JIRA] Closed: (TEIID-183) user "or" and "in" criteria should generate multiple queries in some situations

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-183?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-183. ------------------------------- > user "or" and "in" criteria should generate multiple queries in some situations > ------------------------------------------------------------------------------- > > Key: TEIID-183 > URL: https://jira.jboss.org/browse/TEIID-183 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.x > Reporter: Steven Hawkins > Fix For: 7.0 > > > Defect Tracker #23857: Since web services and relational wrappers around procedures do not support "in" or "or" criteria, an enhancement would be union the results of multipe queries rather than not pushing down the criteria or not validating the query entirely. -- 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1179) Add a CommandContext interface to the teiid api

by Steve Hawkins (JIRA)

Add a CommandContext interface to the teiid api ----------------------------------------------- Key: TEIID-1179 URL: https://jira.jboss.org/browse/TEIID-1179 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 UDFs can use the commandcontext to get additional information about the currently executing query, but it's use in a custom udfs would introduce a dependency on the engine code. We should add a commandcontext interface to the teiid api for use by custom functions. -- 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

14 years, 4 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2010