June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1023) Chanage "MaxResultRows" Connector Property to default to "unlimited"

by Ramesh Reddy (JIRA)

Chanage "MaxResultRows" Connector Property to default to "unlimited" -------------------------------------------------------------------- Key: TEIID-1023 URL: https://jira.jboss.org/jira/browse/TEIID-1023 Project: Teiid Issue Type: Task Components: Connector API Reporter: Ramesh Reddy Fix For: 7.0 Teiid supports a property called "MaxResultRows" in Connector properties, which defaults to 10,000 rows. The expected behavior of this is to throw an exception when user queries more than 10,000 rows through this connector. However, this default behavior seems like a exceptional condition than normal behavior expected by user any time. This *was* designed more for the development time aid than the runtime. Here is an example of community user tripping over it. http://community.jboss.org/message/532560#532560 I propose, we change the default value of this property to "-1" that means the "MaxResultRows" will be set to "unlimited" in the default scenario. If user requires to restrict max rows they can *explicitly* set a value that they are comfortable with. Note the default "unlimited" is value changed from "0" to "-1". -- 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

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIID-939) MySQL nested set query pushdown failure

by Steven Hawkins (JIRA)

MySQL nested set query pushdown failure --------------------------------------- Key: TEIID-939 URL: https://jira.jboss.org/jira/browse/TEIID-939 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 By default our translator is adding parens around nested set queries, this is not supported by MySQL. The parens can safely be dropped as long as both the parent and the child are the same set operation (union, or union all). The only problem for MySQL is that you cannot left nest a union all under a union. -- 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

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-781) Move the CTC testing framework to the teiid community

by Van Halbert (JIRA)

Move the CTC testing framework to the teiid community ----------------------------------------------------- Key: TEIID-781 URL: https://jira.jboss.org/jira/browse/TEIID-781 Project: Teiid Issue Type: Sub-task Reporter: Van Halbert Fix For: 6.2.0 The CTC testing client used by QE for testing MetaMatrix and Teiid needs to be moved to the teiid community. -- 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

14 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-948) Spurious wake-up error with connector work item

by Steven Hawkins (JIRA)

Spurious wake-up error with connector work item ----------------------------------------------- Key: TEIID-948 URL: https://jira.jboss.org/jira/browse/TEIID-948 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 If a synch work items has a spurious wake up, that can cause state exceptions in start/end processing. -- 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

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1084) Exception in BatchIterator

by Steve Hawkins (JIRA)

Exception in BatchIterator -------------------------- Key: TEIID-1084 URL: https://jira.jboss.org/jira/browse/TEIID-1084 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Steve Hawkins Assignee: Steven Hawkins Fix For: 7.0 There's an index out of bounds with buffered resets. -- 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

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Updated: (TEIID-885) CTC vdbs should use appropriate capabilities

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-885?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-885: -------------------------------- Fix Version/s: 7.1 (was: 7.0) > CTC vdbs should use appropriate capabilities > -------------------------------------------- > > Key: TEIID-885 > URL: https://jira.jboss.org/browse/TEIID-885 > Project: Teiid > Issue Type: Quality Risk > Components: Integration Tests > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Warren Gibson > Fix For: 7.1 > > > The CTC test vdbs currently use SimpleCapabilities rather than the actual source capabilities. This means that very little push down support is ever tested by CTC. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1108) Receiving NPE when querying DynamicPortfolio VDB with more complicated query

by Paul Nittel (JIRA)

Receiving NPE when querying DynamicPortfolio VDB with more complicated query ---------------------------------------------------------------------------- Key: TEIID-1108 URL: https://jira.jboss.org/browse/TEIID-1108 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Environment: Fedora 12, Build from 3 June, OpenJDK Runtime Environment (IcedTea6 1.8) (fedora-38.b18.fc12-i386) Reporter: Paul Nittel Assignee: Steve Hawkins I played with the dynamic portfolio VDB and tried to run a query (after deploying a data source based on the VDB). I am able to query the two source within the VDB just fine. In fact, the example's suggested query works: select * from product, (call MarketData.getTextFiles('*.txt')) f, TEXTTABLE(f.file COLUMNS symbol string, price bigdecimal HEADER) price where product.symbol=price.symbol The query is: select LASTNAME, COMPANY_NAME, SHARES_COUNT, PRICE, (SHARES_COUNT * PRICE) AS CurrentValue from holdings,customer, account, product, (call MarketData.getTextFiles('*.txt')) f, TEXTTABLE(f.file COLUMNS symbol string, price bigdecimal HEADER) price where (product.symbol=price.symbol) AND (id = product_id) AND (holdings.account_id = account.account_id) AND (account.ssn = customer.ssn) Eliminating the calculation did not help. And the exception from server.log is: 2010-06-03 09:32:37,263 ERROR [org.teiid.PROCESSOR] (WorkManager(2)-7_QueryProcessorQueue5) Unexpected exception for request lkWFkP39zsZY.4 java.lang.NullPointerException at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.getNDV(NewCalculateCostUtil.java:840) at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.getNDV(NewCalculateCostUtil.java:1077) at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.computeCostForDepJoin(NewCalculateCostUtil.java:967) at org.teiid.query.optimizer.relational.rules.RuleChooseDependent.execute(RuleChooseDependent.java:92) at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:366) at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:167) at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:110) at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:432) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:455) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:349) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:167) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:190) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:187) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:176) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:187) at org.teiid.dqp.internal.process.StatsCapturingWorkManager$WorkWrapper.run(StatsCapturingWorkManager.java:102) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) The error displayed by the JDBC query tool is: org.teiid.jdbc.TeiidSQLException: org.teiid.core.TeiidException at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:109) at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:69) at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:426) at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:329) at org.jboss.resource.adapter.jdbc.WrappedStatement.executeQuery(WrappedStatement.java:226) at JDBCQueryServlet.doPost(JDBCQueryServlet.java:67) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:636) Caused by: [TeiidException] 1 [NullPointerException] at org.teiid.client.ResultsMessage.setException(ResultsMessage.java:177) at org.teiid.dqp.internal.process.RequestWorkItem.sendError(RequestWorkItem.java:522) at org.teiid.dqp.internal.process.RequestWorkItem.attemptClose(RequestWorkItem.java:329) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:214) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:190) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:187) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:176) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:187) at org.teiid.dqp.internal.process.StatsCapturingWorkManager$WorkWrapper.run(StatsCapturingWorkManager.java:102) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) ... 1 more Caused by: java.lang.NullPointerException at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.getNDV(NewCalculateCostUtil.java:840) at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.getNDV(NewCalculateCostUtil.java:1077) at org.teiid.query.optimizer.relational.rules.NewCalculateCostUtil.computeCostForDepJoin(NewCalculateCostUtil.java:967) at org.teiid.query.optimizer.relational.rules.RuleChooseDependent.execute(RuleChooseDependent.java:92) at org.teiid.query.optimizer.relational.RelationalPlanner.executeRules(RelationalPlanner.java:366) at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:167) at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:110) at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:432) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:455) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:349) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:167) ... 11 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1101) Teiid Example PortfolioDS specifies a username & password for Derby source where none is required

by Paul Nittel (JIRA)

Teiid Example PortfolioDS specifies a username & password for Derby source where none is required ------------------------------------------------------------------------------------------------- Key: TEIID-1101 URL: https://jira.jboss.org/browse/TEIID-1101 Project: Teiid Issue Type: Bug Components: Build/Kits Affects Versions: 7.0 Environment: All Reporter: Paul Nittel Assignee: Steve Hawkins The instructions for creating the Derby database used by the portfolio example do not specify creation and use of a username/schema. The portfolio-ds.xml file does, however, specify a username and password. When the user attempts to use this data source, it fails since there is no such schema as "sa". We shold either direct the user to create the schema and user account, or--much simpler--eliminate th use of the username/password from the data source file. On the other hand, my idea of "simple" might not be the right way to go ;-) -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-926) Reduce use of map look ups for projection

by Steven Hawkins (JIRA)

Reduce use of map look ups for projection ----------------------------------------- Key: TEIID-926 URL: https://jira.jboss.org/jira/browse/TEIID-926 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 7.0 GroupingNode, SelectNode, and JoinNode are using map lookups to project tuples. This should be precomputed instead. -- 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

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-898) Named procedure parameter error message too terse.

by Steven Hawkins (JIRA)

Named procedure parameter error message too terse. -------------------------------------------------- Key: TEIID-898 URL: https://jira.jboss.org/jira/browse/TEIID-898 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Optional Fix For: 7.0 The error message for a named procedure "EXEC VirtProcs.dyno( virtprocs.dyno.timein='04:00:00', virtprocs.dyno.byteme=125)" error is Invalid param name(s): [VIRTPROCS.DYNO.BYTEME, VIRTPROCS.DYNO.TIMEIN] which doesn't give any indication as to what names are expected, it just returns the names used in upper case. -- 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

14 years, 7 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010