November 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1818) XMLQuery/XMLTable prepared context type

by Steven Hawkins (Created) (JIRA)

XMLQuery/XMLTable prepared context type --------------------------------------- Key: TEIID-1818 URL: https://issues.jboss.org/browse/TEIID-1818 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 7.6 A query such as "select xmlquery('/a' passing ?)" will not resolve since no type is associated with the parameter. The context item at least should be known to be xml. Other passing clause values are currently allowed to multiple types and would require a cast/convert. -- 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

3
2
0 / 0

[JBoss JIRA] (TEIID-1807) ExecutionContext should be available to ExecutionFactory.getConnect()

by Mark Addleman (Created) (JIRA)

ExecutionContext should be available to ExecutionFactory.getConnect() --------------------------------------------------------------------- Key: TEIID-1807 URL: https://issues.jboss.org/browse/TEIID-1807 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins (I apologize if this is a dup, I have been meaning to submit this for a while and can't remember if I have. I can't find it in Jira) We have data sources which require information from the execution context before in order to provide a connection. In some cases, they require the Subject. In other cases, they will require information from the payload. -- 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

5
5
0 / 0

[JBoss JIRA] Created: (TEIID-1698) + is not properly handled in like patterns

by Steven Hawkins (JIRA)

+ is not properly handled in like patterns ------------------------------------------ Key: TEIID-1698 URL: https://issues.jboss.org/browse/TEIID-1698 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 7.4.1, 7.5 + is not escaped in the generated regular expression, thus matching fails. -- 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] (TEIID-1785) EDS cross join attempting to join on mismatching datatypes

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1785?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1785. --------------------------------- > EDS cross join attempting to join on mismatching datatypes > ---------------------------------------------------------- > > Key: TEIID-1785 > URL: https://issues.jboss.org/browse/TEIID-1785 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > When running a query which appears to be attempting a cross join, from looking at the query plan. This is resulting in an error and stack trace, pointing to the merge join implementation trying to convert from integer to string. > This is when we provide one item to filter on, so it appears EDS is selecting the number 1 to indicate if it is present, and I think this is what it's trying to join to. When providing more than one thing to filter on, so EDS selects the book ID, the query runs. > Good and bad query plans are attached. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1563) Refresh a Materialized View without parameters from admin console

by Stephen Brooks (JIRA)

Refresh a Materialized View without parameters from admin console ----------------------------------------------------------------- Key: TEIID-1563 URL: https://issues.jboss.org/browse/TEIID-1563 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1.1 Environment: EDS on RHEL 5, Admin Console with Firefox 4.0 Reporter: Stephen Brooks Assignee: Steven Hawkins Priority: Minor Found an EDS bug in the admin console where it tries to refresh without parameters. Steps to reproduce: 1. Go to the 'Control' tab for a VDB 2. Click 'Refresh a Materialized View' 3. Don't enter information, just click 'Cancel' 4. Click 'Refresh a Materialized View' again -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
6
0 / 0

[JBoss JIRA] Created: (TEIID-1596) Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval

by Graeme Gillies (JIRA)

Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval --------------------------------------------------------------------------------------------------------------------- Key: TEIID-1596 URL: https://issues.jboss.org/browse/TEIID-1596 Project: Teiid Issue Type: Feature Request Reporter: Graeme Gillies Assignee: Steven Hawkins In the teiid documentation there is no mention (from what I can find) of exactly what the option queryThresholdInSecs does. The xml file states "Long running query threshold, after which a alert can be generated by tooling if configured", what tooling is this exactly? Does it alert and stop the query, or just alert? On the same token, there is the configuration item maxSourceRows which is configured per instance. Unfortunately this isn't flexible enough sometimes, and it would be better if this option could be configured per VDB and per data role as well (some people can get more data than others). I would expect the determination of what maxSourceRows is for a query should be as follows 1) If maxSourceRows is set for the data role the user has, use that (in the case of two data roles with different values, use the largest value) 2) If maxSourceRows is not set on any of the users data role, but set on the vdb, use that value 3) If maxSourceRows is not set on the vdb or any data roles the user has, use the instance setting. Likewise, the setting maxSourceRows should not only be configurable per data role, vdb, instance, but also the setting queryThresholdInSecs, and either that option or another option should be put in place that allows us to hard limit the length of time a query can run. This is because in teiid we want to be able to say users cannot write a big huge query that will take more than X amount of seconds to execute, to stop someone in teiid giving it a huge query and hammering all the backend databases. Configuring this option by vdb and data role (as some people are more trusted and can run longer queries) would be fantastic. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (TEIID-1699) odbc connection fails and crashes vdb that it doesn't respond to

by Michal Harish (JIRA)

odbc connection fails and crashes vdb that it doesn't respond to ----------------------------------------------------------------- Key: TEIID-1699 URL: https://issues.jboss.org/browse/TEIID-1699 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 7.4 Environment: Windows 7 on VMWare JBoss SA 5.1.0.GA Teiid Runtime 7.4.0.Final + a_teiid-patch-7.4.0.Final PostgreSQL 8.04 ODBC driver Reporter: Michal Harish Assignee: Steven Hawkins Priority: Blocker I have succesfully created and deployed vdb through Teiid Designer into the local JBoss server. I can execute the vdb as well and access it via JDBC but when I try to configure it through ODBC PostgreSQL 8.04 driver it crashes the ODBC Manager as well as the vdb server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
6
0 / 0

[JBoss JIRA] (TEIID-501) Add the 'major' DBMS's system catalogs as 'optional' MMX system catalogs to better 'slide-in' to opportunities.

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-501?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-501. -------------------------------- > Add the 'major' DBMS's system catalogs as 'optional' MMX system catalogs to better 'slide-in' to opportunities. > --------------------------------------------------------------------------------------------------------------- > > Key: TEIID-501 > URL: https://issues.jboss.org/browse/TEIID-501 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Connector, Query Engine > Affects Versions: 8.0 > Reporter: Marc Shirley > > Make MetaMatrix look like an Oracle database or a SQL Server database, including system catalogs as well as query grammar. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIID-1823) XMLTable passing scalar subquery fails to evaluate

by Steven Hawkins (Created) (JIRA)

XMLTable passing scalar subquery fails to evaluate -------------------------------------------------- Key: TEIID-1823 URL: https://issues.jboss.org/browse/TEIID-1823 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.6 Using a scalar subquery as a passing argument (for example - "select * from xmltable('/a/b' passing (SELECT xmlelement(name a, xmlAgg(xmlelement(name b, e1))) from pm1.g1) columns val string path '/.') as x" fails because the planner is not looking for suqueries in source nodes. -- 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

3
2
0 / 0

[JBoss JIRA] Created: (TEIID-1685) NullPointerException in ResultsMessage

by RAKESH BALGURI (JIRA)

NullPointerException in ResultsMessage -------------------------------------- Key: TEIID-1685 URL: https://issues.jboss.org/browse/TEIID-1685 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.3 Environment: Windows7, Teiid 7.3 Reporter: RAKESH BALGURI Assignee: Steven Hawkins I am getting a NullPointerException when we execute queries in parallel. The following is the stack trace java.util.concurrent.ExecutionException: java.lang.Exception: Exception org.teiid.jdbc.TeiidSQLException: org.teiid.core.TeiidException occurred on statement SELECT subType, objectInstance, propertyName, propertyValue FROM chorus_metadata.property WHERE objectName=? at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at com.ca.mfui.chorusR2.server.service.ObjectsServiceImpl.getFilterTree(ObjectsServiceImpl.java:178) at com.ca.mfui.chorusR2.server.service.ObjectsServiceImpl.getTreeForSection(ObjectsServiceImpl.java:2366) at com.ca.mfui.chorusR2.server.service.ObjectsServiceImpl.getTreeNodeChildren(ObjectsServiceImpl.java:2622) 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 com.ca.mfui.chorusR2.servlet.ChorusGWTServlet.processCall(ChorusGWTServlet.java:224) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:224) at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:263) at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:178) at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91) at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62) at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168) at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58) at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168) at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58) at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168) at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58) at com.ca.mfui.chorusR2.servlet.TransactionFilter$1.call(TransactionFilter.java:40) at com.ca.mfui.chorusR2.servlet.TransactionFilter$1.call(TransactionFilter.java:35) at com.ca.chorus.server.transaction.TransactionRunner.invoke(TransactionRunner.java:19) at com.ca.chorus.server.transaction.TransactionRunner$$EnhancerByGuice$$c492b72.CGLIB$invoke$0(<generated>) at com.ca.chorus.server.transaction.TransactionRunner$$EnhancerByGuice$$c492b72$$FastClassByGuice$$4cd78c09.invoke(<generated>) at com.google.inject.internal.cglib.proxy.$MethodProxy.invokeSuper(MethodProxy.java:228) at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72) at com.ca.chorus.server.transaction.TransactionalMethodInterceptor.invoke(TransactionalMethodInterceptor.java:23) at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72) at com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52) at com.ca.chorus.server.transaction.TransactionRunner$$EnhancerByGuice$$c492b72.invoke(<generated>) at com.ca.mfui.chorusR2.servlet.TransactionFilter.doFilter(TransactionFilter.java:34) at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163) at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58) at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168) at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58) at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118) at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:387) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:49) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520) Caused by: java.lang.Exception: Exception org.teiid.jdbc.TeiidSQLException: org.teiid.core.TeiidException occurred on statement SELECT subType, objectInstance, propertyName, propertyValue FROM chorus_metadata.property WHERE objectName=? at com.ca.chorus.db.DbExecutor.handleSqlException(DbExecutor.java:285) at com.ca.chorus.db.DbExecutor.withResultSet(DbExecutor.java:264) at com.ca.chorus.db.DbExecutor.gatherResults(DbExecutor.java:416) at com.ca.chorus.db.DbExecutor.gatherResults(DbExecutor.java:410) at com.ca.mfui.chorusR2.server.service.MetadataServiceImpl.getMetadataForObjectNameFromTeiid(MetadataServiceImpl.java:82) at com.ca.mfui.chorusR2.server.service.MetadataServiceImpl.getMetadataFor(MetadataServiceImpl.java:66) at com.ca.mfui.chorusR2.server.service.ObjectsServiceImpl$1.call(ObjectsServiceImpl.java:170) at com.ca.mfui.chorusR2.server.service.ObjectsServiceImpl$1.call(ObjectsServiceImpl.java:1) at com.google.inject.servlet.ServletScopes$3.call(ServletScopes.java:194) at com.ca.chorus.server.transaction.TransactionRunner.invoke(TransactionRunner.java:19) at com.ca.chorus.server.transaction.TransactionalMethodInterceptor.invoke(TransactionalMethodInterceptor.java:23) at com.ca.mfui.chorusR2.server.service.RequestScopedThreadPoolCallableDecorator.call(RequestScopedThreadPoolCallableDecorator.java:38) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) 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) Caused by: 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:497) at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:214) at com.ca.chorus.db.LeakDetectingPreparedStatement.executeQuery(LeakDetectingPreparedStatement.java:46) at com.ca.chorus.db.DbExecutor.withResultSet(DbExecutor.java:231) ... 15 more Caused by: [TeiidException] 1 [NullPointerException] at org.teiid.client.ResultsMessage.setException(ResultsMessage.java:177) at org.teiid.dqp.internal.process.RequestWorkItem.sendError(RequestWorkItem.java:557) at org.teiid.dqp.internal.process.RequestWorkItem.attemptClose(RequestWorkItem.java:335) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:218) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290) ... 3 more Caused by: java.lang.NullPointerException at org.teiid.common.buffer.impl.BufferManagerImpl$ManagedBatchImpl.getBatch(BufferManagerImpl.java:282) at org.teiid.common.buffer.SPage.getValues(SPage.java:161) at org.teiid.common.buffer.SPage.search(SPage.java:78) at org.teiid.common.buffer.STree.find(STree.java:145) at org.teiid.common.buffer.TupleBrowser.init(TupleBrowser.java:102) at org.teiid.common.buffer.TupleBrowser.nextTuple(TupleBrowser.java:168) at org.teiid.query.tempdata.TempTable$QueryTupleSource.nextTuple(TempTable.java:155) at org.teiid.query.processor.relational.SortUtility.initialSort(SortUtility.java:214) at org.teiid.query.processor.relational.SortUtility.sort(SortUtility.java:168) at org.teiid.query.tempdata.TempTable.createTupleSource(TempTable.java:417) at org.teiid.query.tempdata.TempTable.createTupleSource(TempTable.java:398) at org.teiid.query.tempdata.TempTableDataManager.registerQuery(TempTableDataManager.java:437) at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:182) at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:170) at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:197) at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:118) at org.teiid.query.processor.relational.RelationalPlan.open(RelationalPlan.java:152) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:134) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:105) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:115) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:250) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:184) ... 7 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2011