March 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1471) Projection should be minimized prior to view removal

by Steven Hawkins (JIRA)

Projection should be minimized prior to view removal ---------------------------------------------------- Key: TEIID-1471 URL: https://issues.jboss.org/browse/TEIID-1471 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 View removal may be inhibited by the placement of select clause items, such as non-deterministic functions, that are not meaningful to the query. To minimize the work performed by optional join removal and by merge virtual we should run assign output elements prior to merging. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-777) Move the tests from the jbedsp-test-Integration project to the teiid communitiy

by Van Halbert (JIRA)

Move the tests from the jbedsp-test-Integration project to the teiid communitiy ------------------------------------------------------------------------------- Key: TEIID-777 URL: https://jira.jboss.org/jira/browse/TEIID-777 Project: Teiid Issue Type: Sub-task Affects Versions: 6.2.0 Reporter: Van Halbert Assignee: Van Halbert This task is about moviing the jbedsp-test-integration test to the teiid project. As part of this task, will need to setup the framework to install the schema and create tables needed by the tests. Some tests are database dependent and that will need to be taken into account. Therefore, if a developer / contributor tries to run these tests, only those tests that work for the defined database(s) will be run. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (TEIID-1422) Limit pushing can result in inconsistent xml results

by Steven Hawkins (JIRA)

Limit pushing can result in inconsistent xml results ---------------------------------------------------- Key: TEIID-1422 URL: https://issues.jboss.org/browse/TEIID-1422 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1, 7.3 A customer case (00393370) was using rowlimitexception and not actually triggering the exception when expected. This is due to our logic in rulepushlimit that allows an unordered limit to be pushed through union not all, select nodes, or dup removal. While the results may be consistent for some ordering of results there are many situations when you will get back far less results than the limit specifies. The intent was to more broadly push the limit rather than to apply it in a fully consistent manner. However this is problematic for situations, like the rowlimitexception logic that expect an exceptional condition to be triggered if the limit is exceeded. The best fix would be to just not push an unordered limit in these situations, then if the more aggressive pushing is desired by a user we can look at using a hint or some other mechanism to allow the pushing. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-1406) Salesforce connector does not parse {ts'2003-03-11 11:42:10.5'} - gets mismatched character ' ' expecting ':'

by Paul Nittel (JIRA)

Salesforce connector does not parse {ts'2003-03-11 11:42:10.5'} - gets mismatched character ' ' expecting ':' ------------------------------------------------------------------------------------------------------------- Key: TEIID-1406 URL: https://issues.jboss.org/browse/TEIID-1406 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 7.1.1 Reporter: Paul Nittel Assignee: Steven Hawkins Attachments: sfQueryError.txt As part of testing the SalesForce connector, I executed the following query: Select Subject, ClosedDate from Case_ where ClosedDate > {ts'2003-03-11 11:42:10.5'} and got back: Error: Remote org.teiid.core.TeiidProcessingException: MALFORMED_QUERY: > 2003-03-11T11:42:10.500Z-05:00 LIMIT 100 ^ ERROR at Row:1:Column:101 line 1:101 mismatched character ' ' expecting ':' A more complete stack trace is attached. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
7
0 / 0

[JBoss JIRA] Closed: (TEIID-114) Execs of xml procedures cannot be used as correlated scalar subqueries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-114?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-114. -------------------------------- > Execs of xml procedures cannot be used as correlated scalar subqueries > ---------------------------------------------------------------------- > > Key: TEIID-114 > URL: https://issues.jboss.org/browse/TEIID-114 > Project: Teiid > Issue Type: Bug > Components: XML Planner/Processor > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > > Defect Tracker #24364: attempted to run select (exec BooksInfo.getXMLBooksByEdition(edition)) result from booksinfo.booksinfo from the e2e audiobooks and received the following error: > java.lang.NullPointerException > at com.metamatrix.query.processor.xml.RelationalPlanExecutor.<init>(RelationalPlanExecutor.java:67) > at com.metamatrix.query.processor.xml.XMLProcessorEnvironment.createResultExecutor(XMLProcessorEnvironment.java:213) > at com.metamatrix.query.processor.xml.ExecSqlInstruction.process(ExecSqlInstruction.java:35) > at com.metamatrix.query.processor.xml.XMLPlan.getNextXMLChunk(XMLPlan.java:320) > at com.metamatrix.query.processor.xml.XMLPlan.processXML(XMLPlan.java:256) > at com.metamatrix.query.processor.xml.XMLPlan.nextBatch(XMLPlan.java:187) > at com.metamatrix.query.processor.relational.SubqueryProcessorUtility.process(SubqueryProcessorUtility.java:231) > at com.metamatrix.query.processor.relational.DependentProjectNode.prepareToProcessTuple(DependentProjectNode.java:96) > at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:200) > at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:244) > at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:143) > at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:194) > at com.metamatrix.dqp.internal.process.ProcessWorker.processDirect(ProcessWorker.java:159) > at com.metamatrix.dqp.internal.process.ProcessWorker.process(ProcessWorker.java:89) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:64) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-760) Group tuplesources by command

by Steven Hawkins (JIRA)

Group tuplesources by command ----------------------------- Key: TEIID-760 URL: https://jira.jboss.org/jira/browse/TEIID-760 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.x Tuplesource are mostly grouped by session, but it would be better in preventing tuplesource leaks if they were subgrouped by command. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1504) Internal Materialization does not honr the cache hint

by Ramesh Reddy (JIRA)

Internal Materialization does not honr the cache hint ----------------------------------------------------- Key: TEIID-1504 URL: https://issues.jboss.org/browse/TEIID-1504 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.2 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 7.4 When a internal materialization is loaded with /*+ cache(pref_mem ttl:120000)*/ select * from view.g1, to does not refresh/flush the matview contents from memory after two minutes (120000). Upon inspecting the code, it looks like the Cache Hint is being on searched on the created temp table rather than the original query. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1461) Data Services Caching Guide - Problems, issues, etc.

by Van Halbert (JIRA)

Data Services Caching Guide - Problems, issues, etc. ---------------------------------------------------- Key: TEIID-1461 URL: https://issues.jboss.org/browse/TEIID-1461 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 7.1.1 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Blocker The nits are getting even more minor (minorer?) In paragraph 3.5.1, the doc refers to both SYSADMIN.refreshMatView and SYS.refreshMatView. "SYS." should be changed to "SYSADMIN." That's the last one. The doc looks great otherwise! -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] Closed: (TEIID-68) Equivalence expressions in where clauses between two columns are ignored.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-68?page=com.atlassian.jira.plugin.s... ] Steven Hawkins closed TEIID-68. ------------------------------- > Equivalence expressions in where clauses between two columns are ignored. > ------------------------------------------------------------------------- > > Key: TEIID-68 > URL: https://issues.jboss.org/browse/TEIID-68 > Project: Teiid > Issue Type: Bug > Components: XML Connector > Affects Versions: 9.x > Reporter: Steven Hawkins > Priority: Optional > > Defect Tracker #18728: If the where clause processed by the XML connectors has an equivalence expression containing two columns (where col1 = col2), the expression will be ignored. If the expression contains a column and a literal, it works properly. Thus a workaround is to use a scalar conversion function to convert the column to a literal. Something like substring(col1, 0) for string values or (col1 * 1) for numeric values. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1453) Possible load-balancing issue in Teiid

by Boris Belovic (JIRA)

Possible load-balancing issue in Teiid -------------------------------------- Key: TEIID-1453 URL: https://issues.jboss.org/browse/TEIID-1453 Project: Teiid Issue Type: Bug Affects Versions: 7.1.1 Reporter: Boris Belovic Assignee: Steven Hawkins I have 2 SOA-P servers clustered, both with Teiid installed. node1 has property org.teiid.sockets.maxCachedInstances set to 2 node2 has property org.teiid.sockets.maxCachedInstances set to 16 There is a web app deployed on node1 which starts consuming connections from Teiid datasource. When all connections from node1 are used, the app should get a connection from second node. But instead , I have got following exception: 16:06:59,341 ERROR [STDERR] org.jboss.util.NestedSQLException: Unable to get managed connection for TEIID-DS; - nested throwable: (javax.resource.ResourceException: Unable to get managed connection for TEIID-DS) 16:06:59,342 ERROR [STDERR] at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95) 16:06:59,342 ERROR [STDERR] at org.jboss.soa.clustering.teiid.LoadBalancingServlet.getDatasourceConnection(Unknown Source) 16:06:59,342 ERROR [STDERR] at org.jboss.soa.clustering.teiid.LoadBalancingServlet.doGet(Unknown Source) 16:06:59,342 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) 16:06:59,342 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) 16:06:59,342 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 16:06:59,342 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 16:06:59,342 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 16:06:59,342 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) 16:06:59,342 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 16:06:59,342 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) 16:06:59,342 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 16:06:59,342 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183) 16:06:59,342 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95) 16:06:59,342 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) 16:06:59,342 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) 16:06:59,342 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) 16:06:59,342 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 16:06:59,342 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) 16:06:59,342 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 16:06:59,342 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) 16:06:59,342 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) 16:06:59,342 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) 16:06:59,342 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451) 16:06:59,342 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619) 16:06:59,342 ERROR [STDERR] Caused by: javax.resource.ResourceException: Unable to get managed connection for TEIID-DS 16:06:59,342 ERROR [STDERR] at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:441) 16:06:59,342 ERROR [STDERR] at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:424) 16:06:59,343 ERROR [STDERR] at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496) 16:06:59,343 ERROR [STDERR] at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941) 16:06:59,343 ERROR [STDERR] at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89) 16:06:59,343 ERROR [STDERR] ... 24 more 16:06:59,343 ERROR [STDERR] Caused by: javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ) 16:06:59,343 ERROR [STDERR] at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:311) 16:06:59,343 ERROR [STDERR] at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:690) 16:06:59,343 ERROR [STDERR] at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404) 16:06:59,343 ERROR [STDERR] ... 28 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2011