January 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2331) TEIID30019 Unexpected exception for request kfhsdoaNXYfM.1: java.lang.NullPointerException

by Mark Addleman (JIRA)

[ https://issues.jboss.org/browse/TEIID-2331?page=com.atlassian.jira.plugin... ] Mark Addleman commented on TEIID-2331: -------------------------------------- Just to be clear: The query is already cancelled and then the NPE occurs, so the client is not going to miss any results? btw, thanks for dogging this > TEIID30019 Unexpected exception for request kfhsdoaNXYfM.1: java.lang.NullPointerException > ------------------------------------------------------------------------------------------ > > Key: TEIID-2331 > URL: https://issues.jboss.org/browse/TEIID-2331 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.1 > Environment: Windows 7 > Reporter: Sabina Norderhaug > Assignee: Steven Hawkins > Priority: Minor > > We are getting this exception during continious execution. Looks like client cancelling the execution > 16:13:16,171 ERROR [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue902) TEIID30019 Unexpected exception for request kfhsdoaNXYfM.1: java.lang.NullPointerException > at org.teiid.dqp.internal.process.RequestWorkItem.sendResultsIfNeeded(RequestWorkItem.java:753) > at org.teiid.dqp.internal.process.RequestWorkItem$1.flushBatchDirect(RequestWorkItem.java:557) > at org.teiid.query.processor.BatchCollector.flushBatch(BatchCollector.java:191) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:166) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:382) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:291) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:219) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:249) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_03] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_03] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2331) TEIID30019 Unexpected exception for request kfhsdoaNXYfM.1: java.lang.NullPointerException

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2331?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-2331: ----------------------------------- I was able to reproduce this. It does specifically happen in the continuous case when there is a batch delivered after a cancel has taken effect. The continuous check in the results method is causing the check of the receiver to be skipped. > TEIID30019 Unexpected exception for request kfhsdoaNXYfM.1: java.lang.NullPointerException > ------------------------------------------------------------------------------------------ > > Key: TEIID-2331 > URL: https://issues.jboss.org/browse/TEIID-2331 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.1 > Environment: Windows 7 > Reporter: Sabina Norderhaug > Assignee: Steven Hawkins > Priority: Minor > > We are getting this exception during continious execution. Looks like client cancelling the execution > 16:13:16,171 ERROR [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue902) TEIID30019 Unexpected exception for request kfhsdoaNXYfM.1: java.lang.NullPointerException > at org.teiid.dqp.internal.process.RequestWorkItem.sendResultsIfNeeded(RequestWorkItem.java:753) > at org.teiid.dqp.internal.process.RequestWorkItem$1.flushBatchDirect(RequestWorkItem.java:557) > at org.teiid.query.processor.BatchCollector.flushBatch(BatchCollector.java:191) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:166) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:382) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:291) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:219) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:249) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_03] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_03] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-196) Support creation of temp tables on physical sources.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-196?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-196: -------------------------------------- The simplest (lowest effort) design would be an extension of our DDL/temp table syntax: CREATE FOREIGN TEMPORARY TABLE name (...) ON source [AS 'native sql'] The options clauses would specify the name in source etc as appropriate and the native sql would be executed via the native query procedure facility if applicable. This side-steps any need in our language to add support for additional source constructs, such as alternative index types, additional constraints etc. So this would effectively be a hybrid of our internal temp logic and standard pushdown logic. We would also likely have to allow a drop to be specified with native sql. We might want to still perform some metadata import from the source as to not make the full metadata specification too onerous. From the perspective of Teiid this will be treated as a temporary table in so much as it will be session scoped, but there would not need to be a restriction on the source side as to the table type. > Support creation of temp tables on physical sources. > ---------------------------------------------------- > > Key: TEIID-196 > URL: https://issues.jboss.org/browse/TEIID-196 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Ken Johnson > Fix For: 8.3 > > > This is a multi-part request. > First, the system should support creation of temporary tables using a physical backing store rather than buffer manger. Given multi-pass SQL's heavy use of temp tables, buffer manager can easily be overloaded with large interim results stored in temp tables. > Second, this should be a user-configurable behavior. For example, user might be able to choose a system-level or session-level default from among: > -- memory/cache > -- a source represented by a connector binding > -- a distinct temp source defined with it's own connection parameters (possibly another schema in the repository DB instance) > Ideally default selectoin should be override-able at temp table creation time through a DDL extension > In the case where multiple temp tables have been created on a source via connector, the query planner should recognize this and leverage pushdown to the temp store when later query passes access multiple temp tables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2284) Create Teiid RHQ Plugin for Teiid8/AS7/RHQ 4.4

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2284?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2284: ---------------------------------- Fix Version/s: (was: 8.3) Component/s: RHQ Pulling out of the 8.3 release. Needs to be assigned to a release that will correspond to product work. > Create Teiid RHQ Plugin for Teiid8/AS7/RHQ 4.4 > ---------------------------------------------- > > Key: TEIID-2284 > URL: https://issues.jboss.org/browse/TEIID-2284 > Project: Teiid > Issue Type: Task > Components: RHQ > Reporter: Ted Jones > Assignee: Ted Jones > > Need to create a Teiid RHQ plugin that will support Teiid 8.x and run on RHQ 4.4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2232) Update Hive translator for newer version of Hive Driver

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2232?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2232: --------------------------------------- Any update on this? > Update Hive translator for newer version of Hive Driver > ------------------------------------------------------- > > Key: TEIID-2232 > URL: https://issues.jboss.org/browse/TEIID-2232 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.1 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Labels: hive, teiid > Fix For: 8.3 > > > Originally Hive translator designed for 0.7 version of the Hive JDBC driver, the current version is "30 April, 2012: release 0.9.0 available". > Another important update we should do is take advantage of their direct map-reduce job submission through Hive as native command feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2355) BigQuery integration

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2355: ------------------------------------- Summary: BigQuery integration Key: TEIID-2355 URL: https://issues.jboss.org/browse/TEIID-2355 Project: Teiid Issue Type: Feature Request Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: Open To Community http://code.google.com/p/starschema-bigquery-jdbc/ looks promising for simple support of BigQuery. Some of the dependencies could already be in the google-api module. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2355) BigQuery integration

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2355?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2355: ---------------------------------- Component/s: Misc. Connectors > BigQuery integration > -------------------- > > Key: TEIID-2355 > URL: https://issues.jboss.org/browse/TEIID-2355 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: Open To Community > > > http://code.google.com/p/starschema-bigquery-jdbc/ looks promising for simple support of BigQuery. Some of the dependencies could already be in the google-api module. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2035) DeleteDataSource method on Admin API does not completely delete the Connection Factory

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2035?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2035: ---------------------------------- Fix Version/s: (was: 8.3) Moving out of a specific release. These issues depend upon community releases of AS that are still pending. > DeleteDataSource method on Admin API does not completely delete the Connection Factory > -------------------------------------------------------------------------------------- > > Key: TEIID-2035 > URL: https://issues.jboss.org/browse/TEIID-2035 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > > ConnectionFactory requires a two step creation process > 1) create the resource-adaptor section > 2) connection factory section > The delete is removing the (2) and not (1). Thus any subsequent creates using the same name fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2298) Teiid should use the AS7 bom for managing dependencies

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2298?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2298: ---------------------------------- Fix Version/s: (was: 8.3) Moving out of a specific release. These issues depend upon community releases of AS that are still pending. > Teiid should use the AS7 bom for managing dependencies > ------------------------------------------------------- > > Key: TEIID-2298 > URL: https://issues.jboss.org/browse/TEIID-2298 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Attachments: config.txt > > > To be able to build & deploy the productized version of Teiid, it needs to be using the same dependencies as the rest of the platform, dependencies which are defined by http://repo1.maven.org/maven2/org/jboss/as/jboss-as-parent/7.1.2.Final/jb.... > We should try to incorporate this as a bom and test if everything still works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1226) Reuse dynamic sql plans and allow for prepared statements in procedure logic

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1226?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1226: ---------------------------------- Fix Version/s: (was: 8.3) Pulling out of the release. The extra language work does not yet seem to be warranted. Another approach would be to just allow for the use of prepared plans implicitly when using dynamic sql with the using clause. > Reuse dynamic sql plans and allow for prepared statements in procedure logic > ---------------------------------------------------------------------------- > > Key: TEIID-1226 > URL: https://issues.jboss.org/browse/TEIID-1226 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > > Dynamic sql plans (for dynamic sql statements, lookup, and matview refreshes) should allow for plan reuse. > Also procedure logic should have a mechanism to execute prepared statements for further plan reuse. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2013