November 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2882) Add support for Presto DB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2882?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2882: ----------------------------------- Assignee: Ramesh Reddy > Add support for Presto DB > ------------------------- > > Key: TEIID-2882 > URL: https://issues.jboss.org/browse/TEIID-2882 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.10 > > > Presto is an open source distributed SQL query engine for running interactive analytic queries against data sources of all sizes ranging from gigabytes to petabytes. > Presto was designed and written from the ground up for interactive analytics and approaches the speed of commercial data warehouses while scaling to the size of organizations like Facebook. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3219) Excel Translator Wrong Result From Columns With Interleaved Null Values

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3219?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3219: ------------------------------------- Steve, this solution introduces regression, spoke to Kylin about alternate approaches, so he will be submitting another patch soon on this JIRA > Excel Translator Wrong Result From Columns With Interleaved Null Values > ----------------------------------------------------------------------- > > Key: TEIID-3219 > URL: https://issues.jboss.org/browse/TEIID-3219 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Jan Stastny > Assignee: Kylin Soong > Fix For: 8.7.1, 8.10 > > Attachments: artifacts.zip > > > When querying a column which has a null value somewhere in it, the result set is missing all the rows under the null value in the xlsx file. When querying more columns, the result set is missing some values only if there is a row, where both columns contains null value. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2816) HBase Connector/Translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2816?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2816: -------------------------------- Fix Version/s: 8.10 > HBase Connector/Translator > -------------------------- > > Key: TEIID-2816 > URL: https://issues.jboss.org/browse/TEIID-2816 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Connector, JDBC Driver > Affects Versions: Open To Community > Reporter: devin pinkston > Assignee: Kylin Soong > Labels: HBase, Translator > Fix For: 8.10 > > > Develop a HBase translator/connector. Potentially using the Phoenix JDBC driver, supports most SQL and handles connections: > https://github.com/forcedotcom/phoenix -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3219) Excel Translator Wrong Result From Columns With Interleaved Null Values

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3219?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3219. ----------------------------------- Fix Version/s: 8.7.1 8.10 Resolution: Done Thanks Kylin > Excel Translator Wrong Result From Columns With Interleaved Null Values > ----------------------------------------------------------------------- > > Key: TEIID-3219 > URL: https://issues.jboss.org/browse/TEIID-3219 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Jan Stastny > Assignee: Kylin Soong > Fix For: 8.7.1, 8.10 > > Attachments: artifacts.zip > > > When querying a column which has a null value somewhere in it, the result set is missing all the rows under the null value in the xlsx file. When querying more columns, the result set is missing some values only if there is a row, where both columns contains null value. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2883) Support ParAccel as a data source

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2883?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2883: ------------------------------------- ParAccel seems to be gone through acquisition by [http://actian.com] They renamed it, it is has multiple flavors of it * Actian Analytics Platform - Express Hadoop SQL Edition * Actian Analytics Platform - Express Extreme Performance Edition * Actian Analytics Database - Vector Not sure which one? I tried downloading a free version of "Actian Analytics Platform - Express Hadoop SQL Edition" it gave me something called "Ingres" build, looks like following their instructions I could not even install it. More over there is *NO* SQL cook book or document featuring the capabilities of the database. Can we get more details here? > Support ParAccel as a data source > --------------------------------- > > Key: TEIID-2883 > URL: https://issues.jboss.org/browse/TEIID-2883 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Van Halbert > Fix For: 8.10 > > > Support ParAccel as a data source -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-991) Request for support of Sybase IQ as a supported data source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-991?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-991: --------------------------------- Fix Version/s: 8.10 > Request for support of Sybase IQ as a supported data source > ----------------------------------------------------------- > > Key: TEIID-991 > URL: https://issues.jboss.org/browse/TEIID-991 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Marc Shirley > Fix For: 8.10, Open To Community > > > Per client: > We'd like the ability to have a built-in connector type for Sybase IQ, > just the same as Sybase ASE We have been getting inquiries and we've > had to decline one project because we didn't support Sybase IQ out of > the box. We foresee that Sybase IQ will be getting some play within > important Data Warehouses and Data Marts within the firm. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3224) MongoDB: support direct query execution for external materialization use case

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3224?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3224: -------------------------------- Fix Version/s: 8.10 > MongoDB: support direct query execution for external materialization use case > ----------------------------------------------------------------------------- > > Key: TEIID-3224 > URL: https://issues.jboss.org/browse/TEIID-3224 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: tu nguyen > Assignee: Ramesh Reddy > Fix For: 8.10 > > > Use case: to support external mat view in mongoDB, we need to execute query such as: db.collection.remove({}), db.collection.copyTo() to delete & rename staging table. > Teiid currently only support aggregate query: https://issues.jboss.org/browse/TEIID-2740 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3224) MongoDB: support direct query execution for external materialization use case

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3224?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3224: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > MongoDB: support direct query execution for external materialization use case > ----------------------------------------------------------------------------- > > Key: TEIID-3224 > URL: https://issues.jboss.org/browse/TEIID-3224 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: tu nguyen > Assignee: Ramesh Reddy > > Use case: to support external mat view in mongoDB, we need to execute query such as: db.collection.remove({}), db.collection.copyTo() to delete & rename staging table. > Teiid currently only support aggregate query: https://issues.jboss.org/browse/TEIID-2740 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3224) MongoDB: support direct query execution for external materialization use case

by tu nguyen (JIRA)

tu nguyen created TEIID-3224: -------------------------------- Summary: MongoDB: support direct query execution for external materialization use case Key: TEIID-3224 URL: https://issues.jboss.org/browse/TEIID-3224 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Reporter: tu nguyen Assignee: Steven Hawkins Use case: to support external mat view in mongoDB, we need to execute query such as: db.collection.remove({}), db.collection.copyTo() to delete & rename staging table. Teiid currently only support aggregate query: https://issues.jboss.org/browse/TEIID-2740 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3099) RejectedExecutionException for Teiid during high query load

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3099?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3099. --------------------------------- > RejectedExecutionException for Teiid during high query load > ----------------------------------------------------------- > > Key: TEIID-3099 > URL: https://issues.jboss.org/browse/TEIID-3099 > Project: Teiid > Issue Type: Bug > Components: Query Engine, Server > Affects Versions: 8.7 > Environment: Windows (x64) and Mainframe z/OS (x64) > Reporter: Mark Ackert > Assignee: Steven Hawkins > Labels: queryengine, rejectedexecutionexception, teiid-engine, threads > Fix For: 8.7.1, 8.9 > > > Occasionally, when a standalone Teiid server is under high load from concurrent queries, a RejectedExecutionException is thrown. The relevant part of the stacktrace is below. I investigated the ThreadReuseExecutor source, and I believe the issue's cause is based around the sycnhronized(poolLock) code - see below the stack trace for info, and psuedo-code snippet with my analysis below the stacktrace. > Caused by: java.util.concurrent.RejectedExecutionException: Task org.teiid.dqp.internal.process.ThreadReuseExecutor$3@c75a8114 rejected from org.teiid.dqp.internal.process.ThreadReuseExecutor$2@8b1166ec[Running, pool size = 128, active threads = 128, queued tasks = 0, completed tasks = 692637] > at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048) [rt.jar:1.7.0] > at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821) [rt.jar:1.7.0] > at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1372) [rt.jar:1.7.0] > at org.teiid.dqp.internal.process.ThreadReuseExecutor.executeDirect(ThreadReuseExecutor.java:200) [teiid-engine-8.7.0.FinalCAFix-SNAPSHOT.jar:8.7.0.FinalCAFix-SNAPSHOT] > at org.teiid.dqp.internal.process.ThreadReuseExecutor.execute(ThreadReuseExecutor.java:177) [teiid-engine-8.7.0.FinalCAFix-SNAPSHOT.jar:8.7.0.FinalCAFix-SNAPSHOT] > In the below executeDirect, the race condition that appears plausible to me is: given "activeCount" is at the thread pool size limit and a single thread is finishing execution...Let activeCount be reduced by one in the tpe.execute runnable's synchronized block. The synchronized block exits, and goes to the warnWait/logging code - at this point a thread context switch occurs, and a new PrioritizedRunnable (one which isn't waiting on the poolLock at the beginning of the executeDirect method) comes through executeDirect and proceeds forward because "poolLock" has been released, "activeCount" is now sizeLimit-1. The tpe tries to execute a new Runnable wrapping this PrioritizedRunnable, but the previous thread which hasn't completed it's logging code yet is still present in the the threadpool, and as such we get a RejectedExecutionException due to too many threads trying to be executed in a fixed size thread pool. > private void executeDirect(final PrioritizedRunnable command) { > boolean atMaxThreads = false; > synchronized (poolLock) { > .... if activeCount!=max_limit; activeCount++ > } > ....... > tpe.execute(..... > finally { > synchronized (poolLock) { > ....... > activeCont--; > } > if (success) { > ......some log code > } > } -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2014