November 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2726) Query Issue with Hive 0.12 Driver

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2726?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2726: -------------------------------- Fix Version/s: 8.6 Assignee: Ramesh Reddy (was: Steven Hawkins) > Query Issue with Hive 0.12 Driver > --------------------------------- > > Key: TEIID-2726 > URL: https://issues.jboss.org/browse/TEIID-2726 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Fix For: 8.6 > > Attachments: Hive0_12_Issue.txt > > > I set up the latest Hortonworks Sandbox for testing. The latest version uses Hive 0.12. > - I was able to get the hive0.12 driver set up and am able to query successfully from SquirrelSQL. > - Next, I set up the driver in Teiid Designer and was able to successfully import using the "Teiid Connection" importer. > But, when I attempt to query the teiid source the query fails. Query plan and exception are attached. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2723) Teiid 8.6 doesn't work with Cassandra 2.0

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2723?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2723. --------------------------------- Resolution: Cannot Reproduce Bug Tried with 1.0.4 CQL driver, works without any issues. If problem exists re-open with more details. > Teiid 8.6 doesn't work with Cassandra 2.0 > ----------------------------------------- > > Key: TEIID-2723 > URL: https://issues.jboss.org/browse/TEIID-2723 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 8.6 > Environment: Cassandra 2.0.2 with Teiid 8.6 > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Fix For: 8.6 > > > connect Cassandra 2.0.2 through Teiid 8.6 > Exception in thread "main" java.lang.RuntimeException: org.apache.cassandra.exceptions.ConfigurationException: Unable to find abstract-type class 'org.apache.cassandra.db.marshal.TimestampType' > CQL 3.1 driver should works with Cassandra 2.0. > http://www.datastax.com/documentation/cql/3.1/webhelp/index.html -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2726) Query Issue with Hive 0.12 Driver

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIID-2726?page=com.atlassian.jira.plugin... ] Mark Drilling updated TEIID-2726: --------------------------------- Attachment: Hive0_12_Issue.txt Query Plan and exception > Query Issue with Hive 0.12 Driver > --------------------------------- > > Key: TEIID-2726 > URL: https://issues.jboss.org/browse/TEIID-2726 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Steven Hawkins > Attachments: Hive0_12_Issue.txt > > > I set up the latest Hortonworks Sandbox for testing. The latest version uses Hive 0.12. > - I was able to get the hive0.12 driver set up and am able to query successfully from SquirrelSQL. > - Next, I set up the driver in Teiid Designer and was able to successfully import using the "Teiid Connection" importer. > But, when I attempt to query the teiid source the query fails. Query plan and exception are attached. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2722) Cassandra: ORDER BY should do it in memory instead of trying to push down Cassandra in some cases

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2722?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2722. --------------------------------- Cassandra only supports the ORDER By clause when a key is - used in the compoiste index key as second column (partition key) - Then the query has criteria with IN or EQ Took SteveH suggestion and turned the ORDER By completely off. So far my impression is Cassandra's CQL access seems to be very primitive, their original access was based on Thrift clients. If Teiid needs any greater push down (before CQL steps up provides the functionality) we may to look into Thrift based access. > Cassandra: ORDER BY should do it in memory instead of trying to push down Cassandra in some cases > -------------------------------------------------------------------------------------------------- > > Key: TEIID-2722 > URL: https://issues.jboss.org/browse/TEIID-2722 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.6 > Environment: Teiid 8.6 Alpha with Cassandra 1.2.11 > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: Beta2 > Fix For: 8.6 > > > When I tried to join 2 tables together from same keyspace using Teiid 8.6 Alpha with Cassandra 1.2.11. It broke down SQL into 2 CQLs. However, teiid SQL transformer adds order by clause to the CQL which is not supported. > Original SQL: > select "cassandraDS_users"."user_id" as "cassandraDS_users_user_id", > "cassandraDS_invoice"."sale" as "cassandraDS_invoice_sale" > from "cassandraDS"."invoice" "cassandraDS_invoice" > inner join "cassandraDS"."users" "cassandraDS_users" on ("cassandraDS_invoice"."user_id" = "cassandraDS_users"."user_id") > Break Down CQL: > SELECT cassandraDS.invoice.user_id, cassandraDS.invoice.sale FROM cassandraDS.i > nvoice ORDER BY cassandraDS.invoice.user_id > SELECT cassandraDS.users.user_id FROM cassandraDS.users ORDER BY cassandraDS.us > ers.user_id > Error from CQL Driver: > com.datastax.driver.core.exceptions.InvalidQueryException: ORDER BY is only supported when the partition key is restricted by an EQ or an IN. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2726) Query Issue with Hive 0.12 Driver

by Mark Drilling (JIRA)

Mark Drilling created TEIID-2726: ------------------------------------ Summary: Query Issue with Hive 0.12 Driver Key: TEIID-2726 URL: https://issues.jboss.org/browse/TEIID-2726 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.4 Reporter: Mark Drilling Assignee: Steven Hawkins I set up the latest Hortonworks Sandbox for testing. The latest version uses Hive 0.12. - I was able to get the hive0.12 driver set up and am able to query successfully from SquirrelSQL. - Next, I set up the driver in Teiid Designer and was able to successfully import using the "Teiid Connection" importer. But, when I attempt to query the teiid source the query fails. Query plan and exception are attached. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2714) Buffer defrag not working

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2714?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2714: --------------------------------- Fix Version/s: 7.7.9 > Buffer defrag not working > ------------------------- > > Key: TEIID-2714 > URL: https://issues.jboss.org/browse/TEIID-2714 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6, 7.7.9 > > > The defrag task is not working as expected because the header values are written by an object output stream - and not as standalone values into the block data. > For most data usage patterns this isn't an issue as the storage files are self compacting over time due to low block assignments. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2704) DB2 lob values must be read inline

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2704?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2704. ----------------------------------- Resolution: Done Also updated the fix to delay throwing conversion errors until the row is fetched. > DB2 lob values must be read inline > ---------------------------------- > > Key: TEIID-2704 > URL: https://issues.jboss.org/browse/TEIID-2704 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6, 7.7.9 > > > With the DB2 9 driver and selecting a lob column, the resulting instance becomes invalid after the next row of the result is transitioned to. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2725) Group by doesn't work with MongoDB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2725?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2725: -------------------------------- Fix Version/s: 8.4.1 > Group by doesn't work with MongoDB > ---------------------------------- > > Key: TEIID-2725 > URL: https://issues.jboss.org/browse/TEIID-2725 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Environment: Teiid with MongoDB > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.4.1, 8.6 > > > Group by SQL with/ without aggregate function returns incorrect values: > For example: > Original SQL: > select "grade", sum("score") as "sum_score" from "mongoDBDS"."grades" group by "grade" order by "grade" > > Transform query: > SELECT grades.grade AS c_0, SUM(grades.score) AS c_1 FROM grades GROUP BY grades.grade ORDER BY c_0 > $group:{ "_id" : "$grade" , "c_1" : { "$sum" : "$score"}} > $project:{ "c_0" : "$grade" , "c_1" : 1} > $sort:{ "c_0" : 1} > Expected Result: > grade score > A 187 > F 55 > Actual Result: (INCORRECT) > grade score > 242 > It only returns SUM(score) and group by fields are ignore. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2725) Group by doesn't work with MongoDB

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2725?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2725: ------------------------------------ Yes > Group by doesn't work with MongoDB > ---------------------------------- > > Key: TEIID-2725 > URL: https://issues.jboss.org/browse/TEIID-2725 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Environment: Teiid with MongoDB > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.6 > > > Group by SQL with/ without aggregate function returns incorrect values: > For example: > Original SQL: > select "grade", sum("score") as "sum_score" from "mongoDBDS"."grades" group by "grade" order by "grade" > > Transform query: > SELECT grades.grade AS c_0, SUM(grades.score) AS c_1 FROM grades GROUP BY grades.grade ORDER BY c_0 > $group:{ "_id" : "$grade" , "c_1" : { "$sum" : "$score"}} > $project:{ "c_0" : "$grade" , "c_1" : 1} > $sort:{ "c_0" : 1} > Expected Result: > grade score > A 187 > F 55 > Actual Result: (INCORRECT) > grade score > 242 > It only returns SUM(score) and group by fields are ignore. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2725) Group by doesn't work with MongoDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2725?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2725: ---------------------------------- Affects Version/s: 8.4 (was: 8.6) Should this be back ported to 8.4.x? > Group by doesn't work with MongoDB > ---------------------------------- > > Key: TEIID-2725 > URL: https://issues.jboss.org/browse/TEIID-2725 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Environment: Teiid with MongoDB > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.6 > > > Group by SQL with/ without aggregate function returns incorrect values: > For example: > Original SQL: > select "grade", sum("score") as "sum_score" from "mongoDBDS"."grades" group by "grade" order by "grade" > > Transform query: > SELECT grades.grade AS c_0, SUM(grades.score) AS c_1 FROM grades GROUP BY grades.grade ORDER BY c_0 > $group:{ "_id" : "$grade" , "c_1" : { "$sum" : "$score"}} > $project:{ "c_0" : "$grade" , "c_1" : 1} > $sort:{ "c_0" : 1} > Expected Result: > grade score > A 187 > F 55 > Actual Result: (INCORRECT) > grade score > 242 > It only returns SUM(score) and group by fields are ignore. -- 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

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2013