August 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-98) Prepared/CallableStatement parameter indexes are not correct.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-98?page=com.atlassian.jira.plugin.s... ] Steven Hawkins closed TEIID-98. ------------------------------- > Prepared/CallableStatement parameter indexes are not correct. > ------------------------------------------------------------- > > Key: TEIID-98 > URL: https://issues.jboss.org/browse/TEIID-98 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.x > Reporter: Steven Hawkins > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > All parameter indexes are treated as relative rather than absolute. We should not accept values less than 1 and should ensure that the values specified are continuous. > Also, return parameters should be considered index 1 regardless of where they are in the procedure metadata. For example in defer_testDefect24952 in TestMMStoredProcedure ?=call sp.sp_count_rows_between(?, ?) should have a return value at index 1 from the driver perspective, but instead it has index 3. > see also defect 24952 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1694) Add addition ansi sql function support

by Steven Hawkins (JIRA)

Add addition ansi sql function support -------------------------------------- Key: TEIID-1694 URL: https://issues.jboss.org/browse/TEIID-1694 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 7.5 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.5 Add parsing/support for: substring using from/for trim extract -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
3
0 / 0

[JBoss JIRA] (TEIID-1836) NPE running query of Web service (WSDL imported into Relational Model)

by Paul Nittel (Created) (JIRA)

NPE running query of Web service (WSDL imported into Relational Model) ---------------------------------------------------------------------- Key: TEIID-1836 URL: https://issues.jboss.org/browse/TEIID-1836 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4.1 Reporter: Paul Nittel Assignee: Steven Hawkins Attachments: server.log, WsdlToRel_MPS.zip Using the attached project, I executed (from DTP): exec MaybeThisOne.NewProcedure() On the server, I received this exception: 2011-11-18 09:02:53,137 ERROR [org.teiid.CONNECTOR] (Worker18_QueryProcessorQueue105) Connector worker process failed for atomic-request=vMl7hPK9M4Fm.0.10.8 java.lang.NullPointerException at org.apache.cxf.transport.DestinationFactoryManagerImpl.getDestinationFactoryForUri(DestinationFactoryManagerImpl.java:127) at org.apache.cxf.jaxws.ServiceImpl.createEndpointInfo(ServiceImpl.java:510) at org.apache.cxf.jaxws.ServiceImpl.getJaxwsEndpoint(ServiceImpl.java:248) at org.apache.cxf.jaxws.ServiceImpl.createDispatch(ServiceImpl.java:617) at org.apache.cxf.jaxws.ServiceImpl.createDispatch(ServiceImpl.java:598) at javax.xml.ws.Service.createDispatch(Service.java:325) at org.teiid.resource.adapter.ws.WSConnectionImpl.createDispatch(WSConnectionImpl.java:234) at org.teiid.translator.ws.WSProcedureExecution.execute(WSProcedureExecution.java:99) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:264) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:338) at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:80) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:138) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:135) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:121) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:230) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) 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:662) 2011-11-18 09:02:53,138 ERROR [org.teiid.PROCESSOR] (Worker17_QueryProcessorQueue106) Unexpected exception for request vMl7hPK9M4Fm.0 java.lang.NullPointerException at org.apache.cxf.transport.DestinationFactoryManagerImpl.getDestinationFactoryForUri(DestinationFactoryManagerImpl.java:127) at org.apache.cxf.jaxws.ServiceImpl.createEndpointInfo(ServiceImpl.java:510) at org.apache.cxf.jaxws.ServiceImpl.getJaxwsEndpoint(ServiceImpl.java:248) at org.apache.cxf.jaxws.ServiceImpl.createDispatch(ServiceImpl.java:617) at org.apache.cxf.jaxws.ServiceImpl.createDispatch(ServiceImpl.java:598) at javax.xml.ws.Service.createDispatch(Service.java:325) at org.teiid.resource.adapter.ws.WSConnectionImpl.createDispatch(WSConnectionImpl.java:234) at org.teiid.translator.ws.WSProcedureExecution.execute(WSProcedureExecution.java:99) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:264) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:338) at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:80) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:138) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:135) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:121) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:230) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) 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:662) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

8
11
0 / 0

[JBoss JIRA] (TEIID-1709) CLONE - Allow the use of pushdown functions without requiring Java programming

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1709?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1709: ---------------------------------- Fix Version/s: 7.5 Component/s: Query Engine Affects: Documentation (Ref Guide, User Guide, etc.),Release Notes > CLONE - Allow the use of pushdown functions without requiring Java programming > ------------------------------------------------------------------------------ > > Key: TEIID-1709 > URL: https://issues.jboss.org/browse/TEIID-1709 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.4 > Reporter: Bernd Groh > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.5 > > > Currently, in order to use a database function, even if pushdown is required, it is still necessary to add the function interface to a Java class within the connector, and the connector then must be deployed to the server in order to allow for this pushdown function to be used within the Designer. This creates a lot of extra effort every time you want to make use of a new database function. Particularly, given the schema designer doesn't necessarily have access to either the connector code or the server, and then must involve other parties simply to be able to use an additional database function. It would be very beneficial to speedy schema development if that was not necessary, and if, say, the interface could be defined on the Designer side, added to the VDB, and then deployed as part of the VDB. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1651) Due to a change in the JDBC spec on how the use of "AS" in the select statement will now be returned in the getColumnLabel of the ResultSetMetadata, Teiid must provide backwards support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1651?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1651: ---------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.),Compatibility/Configuration,Release Notes > Due to a change in the JDBC spec on how the use of "AS" in the select statement will now be returned in the getColumnLabel of the ResultSetMetadata, Teiid must provide backwards support > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: TEIID-1651 > URL: https://issues.jboss.org/browse/TEIID-1651 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 7.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 7.4.1, 7.5 > > > Teiid has already applied a fix to support the JDBC spec change for when an alias is used in the select clause. The spec change says the "AS" name will now be returned when getColumnLabel() is called, instead of getColumnName(). Unfortunately, this breaks backwards compatibility. To resolve the issue, the JDBC driver, to provide support for backwards compatibility, can allow the user to specify the useJDBC4ColumnNameAndLabelSemantics=true (default is false) property on the url (this is the recommended spec property). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2060) Correct exception toString methods

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2060: ------------------------------------- Summary: Correct exception toString methods Key: TEIID-2060 URL: https://issues.jboss.org/browse/TEIID-2060 Project: Teiid Issue Type: Quality Risk Components: Common Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.7.1 With TEIID-2022 it was noticed that exception toString methods were causing either meaningless or excessive listings in stack traces. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
3
0 / 0

[JBoss JIRA] (TEIID-2089) Issue with enhanced merge join

by Steven Hawkins (JIRA)

12 years, 4 months

4
16
0 / 0

[JBoss JIRA] (TEIID-2102) Update Quickstart to so that the starting of server is specifically identified as a step

by Van Halbert (JIRA)

Van Halbert created TEIID-2102: ---------------------------------- Summary: Update Quickstart to so that the starting of server is specifically identified as a step Key: TEIID-2102 URL: https://issues.jboss.org/browse/TEIID-2102 Project: Teiid Issue Type: Enhancement Components: Documentation Affects Versions: 8.0 Reporter: Van Halbert Assignee: Van Halbert Priority: Minor The starting of the server in the quick start is in the Setup Data Source section. It should be a step that's uniquely identifiable when walking thru the quick start. And for easy of future reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
3
0 / 0

[JBoss JIRA] (TEIID-2100) Add support for typed getObject calls

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2100: ------------------------------------- Summary: Add support for typed getObject calls Key: TEIID-2100 URL: https://issues.jboss.org/browse/TEIID-2100 Project: Teiid Issue Type: Enhancement Components: JDBC Driver Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 8.1 With the new 1.7 support getObject(x, class) signatures were added, but throw a feature not supported exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

[JBoss JIRA] (TEIID-2098) Caching does not interact well with Statement.setMaxRows

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2098: ------------------------------------- Summary: Caching does not interact well with Statement.setMaxRows Key: TEIID-2098 URL: https://issues.jboss.org/browse/TEIID-2098 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.1 Most of the time setting maxRows will cause the plan to not be cachable and the results will be cached/reused regardless of what subsequent maxRows are set to. Finally a general issue is that if the query cannot have maxRows set as a limit (if there is already a limit or it's a procedure call) then the maxRows is ignored. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2012