December 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2501) window functions in view return incorrect results

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2501?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2501. --------------------------------- > window functions in view return incorrect results > ------------------------------------------------- > > Key: TEIID-2501 > URL: https://issues.jboss.org/browse/TEIID-2501 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.5 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.4, 7.7.8 > > > conditions and limits above a view are too broadly allowed to be pushed through a view layer containing window functions. > From the forum posting for example: > {code} > SELECT > "StateProvinceID" > , COUNT(*) OVER (PARTITION BY a."CountryRegionCode") AS num > FROM salestaxrate a > WHERE "TaxType" = 3{code} > returns the correct counts, where as > {code} > SELECT * > FROM > ( > SELECT > "StateProvinceID" > , COUNT(*) OVER (PARTITION BY a."CountryRegionCode") AS num > FROM salestaxrate a > WHERE "TaxType" = 3 > ) x > WHERE "StateProvinceID" = 45 > {code} > returns counts where the state province id condition is applied before the windowing. > The currently logic will only prevent the criteria from being pushed if it is directly applied against a computed window value. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2568) Order by is omitted when projection is raised above ordering with grouping

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2568?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2568. --------------------------------- > Order by is omitted when projection is raised above ordering with grouping > -------------------------------------------------------------------------- > > Key: TEIID-2568 > URL: https://issues.jboss.org/browse/TEIID-2568 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Environment: Windows and teiid 8.1 > Reporter: Rakesh Balguri > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.1, 8.5, 7.7.8 > > Attachments: Query_Plan_SQL_1.txt, Query_Plan_SQL_2.txt > > > I have a SQL which contain constants in the Select clause and also it contains Group By, Order By and Limit clauses in the SQL. > When I execute the SQL, the Order By clause is not being pushed to the underlying translator. My translator doesn't support "SelectExpressions" i.e. supportsSelectExpression() returns false. > When I remove the constant from the Select clause then the Order By is pushed to the translator. > > Is this a bug in Teiid's query Optimizer? > > The following are the sample queries and attached are the Query Plans for both the SQL's. > > Query1: This SQL doesn't push the Order By clause to the translator. > > SELECT B.RESCLASS, COUNT(*) AS GROUPING_COUNT, 'SECURITY.BASERULE' AS "__objecttype__" FROM > SECURITY.BASERULE AS B GROUP BY B.RESCLASS ORDER BY B.RESCLASS DESC LIMIT 22 > > Query2: This SQL pushes the Order By to the translator. > > SELECT B.RESCLASS, COUNT(*) AS GROUPING_COUNT FROM > SECURITY.BASERULE AS B GROUP BY B.RESCLASS ORDER BY B.RESCLASS DESC LIMIT 22 -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-1092) Request to have variables at higher scopes

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1092?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1092. --------------------------------- > Request to have variables at higher scopes > ------------------------------------------ > > Key: TEIID-1092 > URL: https://issues.jboss.org/browse/TEIID-1092 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.4 > > > Customer is requesting a global or session scoped variable. They want the variable to persist outside of one procedure to other spawned procedures and subsequent queries. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2602) Add clearer message that a VDB cannot be deployed without a JNDI name specified in the .vdb

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2602?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2602. --------------------------------- > Add clearer message that a VDB cannot be deployed without a JNDI name specified in the .vdb > ------------------------------------------------------------------------------------------- > > Key: TEIID-2602 > URL: https://issues.jboss.org/browse/TEIID-2602 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.4.1, 8.5 > > > Created a sample VDB in designer, for which the model is to use the loopback connector. Did not specify a JNDI reference, because it doesn't need one. However, the VDB can't be deployed from Designer because there's no connection info for this model. So I hand deployed, but the server doesn't like it that there's no JNDI specified (if I add the JNDI reference, it deploys fine). You get this error: > 08:10:17,265 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."Sample.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Sample.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Sample.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for java > at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceName.append(ServiceName.java:112) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.as.naming.deployment.ContextNames.buildServiceName(ContextNames.java:183) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:195) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:186) > at org.jboss.as.naming.deployment.ContextNames.bindInfoFor(ContextNames.java:300) > at org.teiid.jboss.VDBDeployer.addDataSourceListener(VDBDeployer.java:245) > at org.teiid.jboss.VDBDeployer.dataSourceDependencies(VDBDeployer.java:267) > at org.teiid.jboss.VDBDeployer.deploy(VDBDeployer.java:153) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > ... 5 more > Can Teiid preempt this and produce a clearer message that its because there's no JNDI specified? -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2500) Rewrite of case with true condition is not correct

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2500?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2500. --------------------------------- > Rewrite of case with true condition is not correct > -------------------------------------------------- > > Key: TEIID-2500 > URL: https://issues.jboss.org/browse/TEIID-2500 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4, 7.7.8 > > > If a secondary searched case condition is always true, then the case will be inappropriately rewritten as just the then expression: > case when ... when true then x else y end > becomes just > x > However the prior cases should still be considered. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2616) The error should be clearer when making a non-ssl connecting to an ssl server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2616?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2616. --------------------------------- > The error should be clearer when making a non-ssl connecting to an ssl server > ----------------------------------------------------------------------------- > > Key: TEIID-2616 > URL: https://issues.jboss.org/browse/TEIID-2616 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > When making a non-ssl connection to an ssl server the message is not indicative of what the issue may be. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2600) IllegalArgumentException when creating datasource from an imported Webservice source model

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2600?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2600. --------------------------------- > IllegalArgumentException when creating datasource from an imported Webservice source model > ------------------------------------------------------------------------------------------ > > Key: TEIID-2600 > URL: https://issues.jboss.org/browse/TEIID-2600 > Project: Teiid > Issue Type: Quality Risk > Components: AdminApi > Affects Versions: 8.0 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > After importing from a remote web service and creating the source and view models, tried to (right click on source model) create data source on teiid server (EAP 6.1 / Teiid 8.4.1) and had this issue: > !ENTRY org.teiid.designer.dqp.ui 4 0 2013-07-25 16:59:24.847 > !MESSAGE Error creating data source for model CustomerRESTWebSvcSource.xmi > !STACK 0 > java.lang.IllegalArgumentException: The argument value is not specified for value: '' > at org.jboss.as.cli.operation.impl.DefaultOperationRequestBuilder.addProperty(DefaultOperationRequestBuilder.java:113) > at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1397) > at org.teiid.adminapi.AdminFactory$AdminImpl.addConfigProperty(AdminFactory.java:308) > at org.teiid.adminapi.AdminFactory$AdminImpl.createConnectionFactory(AdminFactory.java:297) > at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:412) > at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324) > at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551) > at org.teiid.designer.runtime.ui.connection.CreateDataSourceAction.run(CreateDataSourceAction.java:156) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) > 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$5.handleEvent(ActionContributionItem.java:411) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > 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:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > 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:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2517) Incorrect handling of Complex Type in OData Metadata Procedures

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2517?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2517. --------------------------------- > Incorrect handling of Complex Type in OData Metadata Procedures > --------------------------------------------------------------- > > Key: TEIID-2517 > URL: https://issues.jboss.org/browse/TEIID-2517 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: CR2 > Fix For: 8.4 > > > FunctionImports that return ComplexTypes are not being handled correctly. The metadata load fails during the VDB deploy. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2612) Teiid ODBC compatibility with perl-DBD-Pg for postgresql is broken

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2612?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2612. --------------------------------- > Teiid ODBC compatibility with perl-DBD-Pg for postgresql is broken > ------------------------------------------------------------------ > > Key: TEIID-2612 > URL: https://issues.jboss.org/browse/TEIID-2612 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.5 > Reporter: Graeme Gillies > Assignee: Steven Hawkins > Fix For: 8.5 > > > Hi, > We are testing the git head of teiid 8.5 in JBoss EAP 6.1, running with java 7, and are attempting to connect to teiid using perl-DBD-Pg. > We have a code snippet that looks like > {noformat} > #! /usr/bin/perl > use strict; > use warnings; > use DBI; > my $db_type = 'Pg'; > my $db_name = 'TestZipVDB'; > my $db_host = 'teiid.host'; > my $db_port = 5432; > my $user = 'teiid'; > my $pass = 'teiid'; > my $attr = { AutoCommit => 0, RaiseError => 1 }; > my $dsn = sprintf( "dbi:%s:dbname=%s;host=%s;port=%s;sslmode=prefer", > $db_type, $db_name, $db_host, $db_port ); > my $dbh = DBI->connect( $dsn, $user, $pass, $attr ); > my $query = <<QUERY; > select count(1) from bugzilla.bugs > QUERY > my $sth = $dbh->prepare($query); > $sth->execute(); > while ( my @row = $sth->fetchrow_array() ) { > print join( ',', map {"\"$_\""} @row ) . "\n"; > } > $sth->finish(); > $dbh->disconnect(); > {noformat} > However when running this with ssl turned on or off we get the following error > {noformat} > DBD::Pg::st execute failed: unexpected response from server; first received character was "s" at ./a.pl line 25. > DBD::Pg::st execute failed: unexpected response from server; first received character was "s" at ./a.pl line 25. > Issuing rollback() due to DESTROY without explicit disconnect() of DBD::Pg::db handle dbname=TestZipVDB;host=teiid.host;port=5432 at ./a.pl line 25. > {noformat} > It seems that ODBC/Pg Compatibility was broken with a recent commit? > We git this error on a RHEL-6 box running postgresql 8.4 and on Fedora 19 running postgresql 9.2 > Regards, > Graeme -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2294) Allow to use alias name to lookup the certificate from keysore at jdbc ssl transport layer

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2294?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2294. --------------------------------- > Allow to use alias name to lookup the certificate from keysore at jdbc ssl transport layer > ------------------------------------------------------------------------------------------ > > Key: TEIID-2294 > URL: https://issues.jboss.org/browse/TEIID-2294 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Jack Ma > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > From the teiid 8.1 schema (jboss-teiid.xsd) under docs, there is no "alias" attribute defined for jdbc transport layer. Here is the question: in the case of there are multiple certificates defined at keysore, what certificate jdbc ssl will use? How to specify correct one to use? > > Here is the sample teiid jdbc configuration used: > <transport name="jdbc" socket-binding="teiid-jdbc"> > <authentication security-domain="mysecuritydomain"/> > <ssl mode="enabled" keymanagement-algorithm="SunX509"> > <keystore name="/opt/test.keystore" password="password"/> > </ssl> > </transport> -- 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2013