November 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1671) Need to add a place holder for the future deployment of Netezza

by Van Halbert (JIRA)

Need to add a place holder for the future deployment of Netezza --------------------------------------------------------------- Key: TEIID-1671 URL: https://issues.jboss.org/browse/TEIID-1671 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 7.4.1 Reporter: Van Halbert Assignee: Ramesh Reddy Priority: Blocker Fix For: 7.4.1 Add a place holder in 7.4.x for the ability to slide in Netezza when it becomes available. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
3
0 / 0

[JBoss JIRA] (TEIID-1843) StackOverflow using a changing expression as a boolean condition

by Steven Hawkins (Created) (JIRA)

StackOverflow using a changing expression as a boolean condition ---------------------------------------------------------------- Key: TEIID-1843 URL: https://issues.jboss.org/browse/TEIID-1843 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.6 If a changing value is used as a condition directly, e.g. col = case when changing.y then ... The rewriter will fail to replace the changing value and we will continually attempt to rewrite the base update as a loop procedure. -- 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

13 years, 7 months

3
2
0 / 0

[JBoss JIRA] (TEIID-1771) 7.3 or older clients see the wrong column metadata

by Steven Hawkins (Created) (JIRA)

7.3 or older clients see the wrong column metadata -------------------------------------------------- Key: TEIID-1771 URL: https://issues.jboss.org/browse/TEIID-1771 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4.1, 7.6 The fix for TEIID-1534 corrected column name vs. column label. However 7.3 clients use the column name and label interchangeably and typically uses column name. When running against 7.4 or later the column name needs to be reported as the label for legacy clients to work appropriately. -- 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

13 years, 7 months

3
2
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

13 years, 7 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

13 years, 7 months

8
11
0 / 0

[JBoss JIRA] Created: (TEIID-1560) Add support for user defined / pushdown aggregate functions

by Steven Hawkins (JIRA)

Add support for user defined / pushdown aggregate functions ----------------------------------------------------------- Key: TEIID-1560 URL: https://issues.jboss.org/browse/TEIID-1560 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 Add support for user defined aggregate functions. This would also affect the function model metadata. Our aggregate handling logic will need to be generalized to make this possible. Starting with the parser we've got special handling for built-in aggregates. for user defined aggregate handling just a static method will not work as the function needs to retain state across each group. Could require that the implementing class extends AggregateFunction. Could also allow user defined aggregates to take an order by clause. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1328) API request: Programatically modify the VDB

by Mark Addleman (JIRA)

API request: Programatically modify the VDB -------------------------------------------- Key: TEIID-1328 URL: https://jira.jboss.org/browse/TEIID-1328 Project: Teiid Issue Type: Feature Request Components: AdminApi Affects Versions: 7.1 Reporter: Mark Addleman Assignee: Steven Hawkins Priority: Minor I'd like an API to programatically modify the VDB. It would be ideal to modify the VDB using DDL through Teiid. Our primary use case is accessing a dynamic set of datasources through Teiid. When a datasource is added, we would INSERT the appropriate entries into MODEL, PROPERTIES, DATASOURCES tables. Teiid would reread the appropriate metadata from the associated translators. -- 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

13 years, 9 months

6
35
0 / 0

[JBoss JIRA] (TEIID-1854) OData server

by Mark Addleman (Created) (JIRA)

OData server ------------ Key: TEIID-1854 URL: https://issues.jboss.org/browse/TEIID-1854 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins Priority: Minor Teiid should act as an OData server as well as a JDBC server. This is not TEIID-1757 as that is about Teiid being an OData client. -- 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

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] (TEIID-1801) Async Event Processing: Reset and Re-run plan

by Mark Addleman (Created) (JIRA)

Async Event Processing: Reset and Re-run plan ---------------------------------------------- Key: TEIID-1801 URL: https://issues.jboss.org/browse/TEIID-1801 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins In order to processing a stream of events aggregated within a specified time window, the engine should provide some way of specifying the time period (analogous to a window), reset and re-rerun the plan for every time period. There should also be an engine to translator callback indicating that the plan has been reset as opposed to closed. -- 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

13 years, 10 months

8
10
0 / 0

[JBoss JIRA] (TEIID-1852) Salesforce Translator doesnt handle Time types

by Mark Drilling (Created) (JIRA)

Salesforce Translator doesnt handle Time types ---------------------------------------------- Key: TEIID-1852 URL: https://issues.jboss.org/browse/TEIID-1852 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 7.6 Reporter: Mark Drilling Assignee: Steven Hawkins Attachments: SFTestVDB.vdb Query the BusinessHours table imported from Salesforce, which contains columns with 'time' datatype. For example, the query: SELECT Name,CreatedDate,MondayStartTime FROM SFTest.salesforce.BusinessHours Results in: Error Code:ERR.003.029.0025 Message:Failed to transform String to Time. Expected format = hh:mm:ss for 08:00:00.000Z It looks like the code in QueryExecutionImpl.getCellDatum needs to handle translation of the salesforce time format -- 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

13 years, 10 months

6
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2011