May 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-816) XML-Relational File connector throws NPE.

by John Doyle (JIRA)

XML-Relational File connector throws NPE. ----------------------------------------- Key: TEIID-816 URL: https://jira.jboss.org/jira/browse/TEIID-816 Project: Teiid Issue Type: Bug Components: XML Connector Affects Versions: 6.2.0 Reporter: John Doyle Assignee: John Doyle Fix For: 6.2.0 The XML-Relational File connector is throwing an NPE on start up because the caching Boolean is null. -- 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

15 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-605) Push down query results different than MetaMatrix query results without push down - Oracle 11

by Warren Gibson (JIRA)

Push down query results different than MetaMatrix query results without push down - Oracle 11 ---------------------------------------------------------------------------------------------- Key: TEIID-605 URL: https://jira.jboss.org/jira/browse/TEIID-605 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Environment: Running Teiid Server on Windows CTC Query testing client on Windows Reporter: Warren Gibson Assignee: Steven Hawkins This may not be a bug but may just be a decision point to determine if MetaMatrix should guarantee the same query results as if the query was pushed down to the source. In some cases different results can be expected from different DBMS sources. 1. Running Teiid Server with Console Extension Capability Class set to default (blank). 2. Run queries against Oracle 11 source. 3. Results show many examples where "nulls" are being handled differently in a push down ORDER BY situation than what our expected results reflect. 4. Basically in the Oracle 11 situation the "nulls" are showing up in the results just opposite from what MetaMatrix does. In other words in the following query "Select BQT1.SmallA.IntNum From BQT1.SmallA ORDER BY BQT1.SmallA.IntNum DESC" push down results shows "nulls" at the beginning of results whereas without push down MetaMatrix will show the "nulls" at the end of the results. 5. See attached results from this query. -- 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

15 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-817) XML-Relational connector is not handling = criteria.

by John Doyle (JIRA)

XML-Relational connector is not handling = criteria. ---------------------------------------------------- Key: TEIID-817 URL: https://jira.jboss.org/jira/browse/TEIID-817 Project: Teiid Issue Type: Bug Affects Versions: 6.1.0, 6.2.0 Reporter: John Doyle Assignee: John Doyle Fix For: 6.2.0 All XML-R connectors are ignoring = criteria passed in queries. -- 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

15 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (TEIID-486) MOD() scalar function should be supported by DB2 Connector

by Larry O'Leary (JIRA)

MOD() scalar function should be supported by DB2 Connector ---------------------------------------------------------- Key: TEIID-486 URL: https://jira.jboss.org/jira/browse/TEIID-486 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 6.0.0, 6.1.0 Reporter: Larry O'Leary Assignee: Steven Hawkins An issue was logged in where a function that resulted in the use of the mod() scalar function would result in a different query plan causing the queries criteria not to be pushed-down to the source. It appears the cause of the misbehaved query plan was the DB2 connector not supporting the MOD() scalar function. -- 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

15 years, 10 months

4
17
0 / 0

[JBoss JIRA] Created: (TEIID-852) Oracle timestamp to time conversion null handling

by Steven Hawkins (JIRA)

Oracle timestamp to time conversion null handling ------------------------------------------------- Key: TEIID-852 URL: https://jira.jboss.org/jira/browse/TEIID-852 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3.0 Null values are converted to the default time of 00:00:00, this is due to oracle's concat function that returns an empty string with a null input. -- 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-813) Perform bound checking on narrowing numeric conversions

by Steven Hawkins (JIRA)

Perform bound checking on narrowing numeric conversions ------------------------------------------------------- Key: TEIID-813 URL: https://jira.jboss.org/jira/browse/TEIID-813 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 In order to be more compatible with source type systems we should range check numeric conversions. This will also allow for such conversion to not be marked as narrowing for the purposes of rewrite (but they will still not be implicit due to the possible exception). -- 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-794) Simplify functionmodifier

by Steven Hawkins (JIRA)

Simplify functionmodifier ------------------------- Key: TEIID-794 URL: https://jira.jboss.org/jira/browse/TEIID-794 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.3.0 It is no longer necessary to have both a modify and a translate method, since translate can be used to return the function itself. Making this simplification prevents confusing problems such as changing a function name in modify and then having translate not be applied. -- 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

15 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-810) Error executing "limit ?" against Teiid via Hibernate

by Ted Jones (JIRA)

Error executing "limit ?" against Teiid via Hibernate ----------------------------------------------------- Key: TEIID-810 URL: https://jira.jboss.org/jira/browse/TEIID-810 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0, 6.0.0, 6.2.0 Reporter: Ted Jones Assignee: Steven Hawkins [STDOUT] Hibernate: select holdings0_.TRANSACTION_ID as TRANSACT1_188_, holdings0_.SHARES_COUNT as SHARES2_188_, holdings0_.ACCOUNT_ID as ACCOUNT5_188_, holdings0_.PRODUCT_ID as PRODUCT4_188_, holdings0_.PURCHASE_DATE as PURCHASE3_188_ from portfolio.Accounts.HOLDINGS holdings0_ limit ? 14:22:25,518 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: 38000 14:22:25,518 ERROR [JDBCExceptionReporter] Error Code:ERR.015.006.0033 Message:Unable to evaluate ?: No value was available 14:22:25,522 ERROR [STDERR] Aug 28, 2009 2:22:25 PM com.sun.facelets.FaceletViewHandler handleRenderException SEVERE: Error Rendering View[/holdingsList.xhtml] javax.el.ELException: /holdingsList.xhtml: Error reading 'resultList' on type org.domain.aportfolio.session.holdingsList_$$_javassist_seam_4 at com.sun.facelets.compiler.TextInstruction.write(TextInstruction.java:48) at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:280) at org.richfaces.renderkit.html.PanelRenderer.doEncodeBegin(PanelRenderer.java:189) at org.richfaces.renderkit.html.PanelRenderer.doEncodeBegin(PanelRenderer.java:148) at org.ajax4jsf.renderkit.RendererBase.encodeBegin(RendererBase.java:101) at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:813) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:934) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:942) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:592) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:100) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:176) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:109) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) 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:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) 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:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:619) Caused by: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:629) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:73) at org.jboss.seam.framework.EntityQuery.initResultList(EntityQuery.java:80) at org.jboss.seam.framework.EntityQuery.getResultList(EntityQuery.java:71) 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.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:32) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.transaction.TransactionInterceptor$1.work(TransactionInterceptor.java:97) at org.jboss.seam.util.Work.workInTransaction(Work.java:47) at org.jboss.seam.transaction.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:91) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:185) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:103) at org.domain.aportfolio.session.holdingsList_$$_javassist_seam_4.getResultList(holdingsList_$$_javassist_seam_4.java) 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 javax.el.BeanELResolver.getValue(BeanELResolver.java:62) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72) at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) at org.jboss.el.parser.AstEmpty.getValue(AstEmpty.java:29) at org.jboss.el.parser.AstChoice.getValue(AstChoice.java:27) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at com.sun.facelets.el.ELText$ELTextVariable.writeText(ELText.java:184) at com.sun.facelets.el.ELText$ELTextComposite.writeText(ELText.java:108) at com.sun.facelets.compiler.TextInstruction.write(TextInstruction.java:45) ... 56 more Caused by: org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.exception.SQLStateConverter.handledNonSpecific 14:22:25,522 ERROR [STDERR] Exception(SQLStateConverter.java:103) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:2223) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104) at org.hibernate.loader.Loader.list(Loader.java:2099) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:378) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:338) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:64) ... 92 more Caused by: com.metamatrix.jdbc.MMSQLException: Error Code:ERR.015.006.0033 Message:Unable to evaluate ?: No value was available at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:123) at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:71) at com.metamatrix.jdbc.MMStatement.executeSql(MMStatement.java:433) at com.metamatrix.jdbc.MMPreparedStatement.executeQuery(MMPreparedStatement.java:210) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:342) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186) at org.hibernate.loader.Loader.getResultSet(Loader.java:1787) at org.hibernate.loader.Loader.doQuery(Loader.java:674) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.doList(Loader.java:2220) ... 100 more Caused by: [MetaMatrixComponentException] ERR.015.006.0033: Error Code:ERR.015.006.0033 Message:Unable to evaluate ?: No value was available at com.metamatrix.query.eval.Evaluator.getContext(Evaluator.java:673) at com.metamatrix.query.eval.Evaluator.internalEvaluate(Evaluator.java:552) at com.metamatrix.query.eval.Evaluator.evaluate(Evaluator.java:514) at com.metamatrix.query.eval.Evaluator.evaluate(Evaluator.java:97) at com.metamatrix.query.processor.relational.LimitNode.open(LimitNode.java:112) at com.metamatrix.query.processor.relational.RelationalPlan.open(RelationalPlan.java:101) at com.metamatrix.query.processor.QueryProcessor.initialize(QueryProcessor.java:113) at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:153) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:261) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:207) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) ... 1 more -- 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

15 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-798) Add support for unknown keyword parsing

by Steven Hawkins (JIRA)

Add support for unknown keyword parsing --------------------------------------- Key: TEIID-798 URL: https://jira.jboss.org/jira/browse/TEIID-798 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Optional Fix For: 6.2.0 We already support the TRUE and FALSE keywords, we should add support for UNKNOWN as well. UNKNOWN is the same as convert(null, boolean). The stringtoboolean conversion should also support UNKNOWN. -- 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-800) Teiid char type should be consistently treated as char(1)

by Steven Hawkins (JIRA)

Teiid char type should be consistently treated as char(1) --------------------------------------------------------- Key: TEIID-800 URL: https://jira.jboss.org/jira/browse/TEIID-800 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 It looks like there was some initial design confusion with the Teiid character type in that it should map to the SQL char type (more specifically char(1)). However we added the restriction that an empty string produces an exception. This behavior is not supported by any database. To make the type consistent with sources and to allow for eventually supporting lengths other than 1, we should treat our char type as char(1) - for the stringtochar conversion we convert empty string to ' ' and the ascii function should return null for empty string (that's the common behavior for Sybase/SQL Server/Oracle but MySQL returns 0). -- 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

15 years, 10 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2010