[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
14 years, 1 month
[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
14 years, 1 month
[JBoss JIRA] Created: (TEIID-745) Ensure string parsing routines are consistent
by Steven Hawkins (JIRA)
Ensure string parsing routines are consistent
---------------------------------------------
Key: TEIID-745
URL: https://jira.jboss.org/jira/browse/TEIID-745
Project: Teiid
Issue Type: Quality Risk
Components: Common, Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.2.0
String parsing strictness varies depending upon whether a convert or a parse function is used. In short we should:
1. Perform a trim prior to parsing (double and float converts already do this implicitly)
2. Use all non-whitespace characters in the parse string - the DateFormat, NumberFormat, and most of the convert methods allow for junk to appear after a successful parsing.
3. Time/Date/Timestamps should use non lenient parsing to disallow dates that are out of range, i.e. 2007-13-35
--
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, 1 month
[JBoss JIRA] Created: (TEIID-684) Dynamic data integration feature (Integrate data with out a VDB)
by Ramesh Reddy (JIRA)
Dynamic data integration feature (Integrate data with out a VDB)
----------------------------------------------------------------
Key: TEIID-684
URL: https://jira.jboss.org/jira/browse/TEIID-684
Project: Teiid
Issue Type: Feature Request
Components: Connector API, Query Engine
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Priority: Critical
Fix For: 6.3.0
This is feature request for dynamically integrating the data with out any modelling exercise, so that any tooling is not required before you can start integrating data.
Using this feature, the user would create/define a Connectors (data sources) in the Teiid runtime engine, and then user connects to runtime engine using the JDBC driver provided, then he/she can start writing SQL queries that spans multiple data sources in a single statement as if they are single source.
For example:
Data Source: A has
TableA1
TableA2
DataSource: B has
TableB1
TableB2
user can write SQL queries such as
SELECT A.TableA1.e1, A.TableA1.e2, B.TableB1.e1, B.TableB1.e2 FROM A.TableA1, B.TableB1 WHERE A.TableA1.e1 = B.TableB1.e1
They can much more complex join queries than above too.
--
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, 1 month
[JBoss JIRA] Created: (TEIID-787) Merge Oracle Spatial Connector functionality into Oracle Connector
by Larry O'Leary (JIRA)
Merge Oracle Spatial Connector functionality into Oracle Connector
------------------------------------------------------------------
Key: TEIID-787
URL: https://jira.jboss.org/jira/browse/TEIID-787
Project: Teiid
Issue Type: Task
Components: JDBC Connector
Affects Versions: 6.2.0
Reporter: Larry O'Leary
Assignee: Steven Hawkins
It seems that the Oracle Spatial Connector is an extension of the Oracle Connector. Because it is an extension and the functionality, translators, capabilities, etc, are the same it means we need to manage the same connector in two different places not to mention have the same dependencies required and offered by two different packages.
Because of this duplication, I recommend that the Oracle Spatial Connector be merged with the Oracle Connector. This should be as simple as merging the supported functions defined by the Oracle Spatial Connector with the Oracle Connector and migrating Oracle Spatial specific unit tests.
Because the functions offered by the Oracle Spatial Connector are not system functions, the function definition for the Oracle Spatial functions should be kept separate and offered to the user as a post installation task if they choose to use spatial functions.
For example, if a user decides to use Oracle as a data source, they would choose the Oracle Connector regardless of whether or not they planned on using spatial functions. The connector binding configuration would be the same in either case. If the user requires the use of the spatial functions, the only post-installation/configuration step would be to install the Oracle Spatial Function Definitions into their Teiid run-time environment or into Teiid Designer to make them available at design-time.
--
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, 1 month