January 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2803) Provide SAML support for OData Transport

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2803: ----------------------------------- Summary: Provide SAML support for OData Transport Key: TEIID-2803 URL: https://issues.jboss.org/browse/TEIID-2803 Project: Teiid Issue Type: Feature Request Components: OData Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.7 Provide SAML based security authentication support for OData transport. Provide a capability for user to configure their own STS provider. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2673) CNF exception when getting data through infinispan-cache translator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2673?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2673: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1011502|https://bugzilla.redhat.com/show_bug.cgi?id=1011502] from MODIFIED to ON_QA > CNF exception when getting data through infinispan-cache translator > ------------------------------------------------------------------- > > Key: TEIID-2673 > URL: https://issues.jboss.org/browse/TEIID-2673 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Labels: infinispan > Fix For: 8.4.1, 8.7 > > > When getting data through infinispan-cache translator using remote hot rod access, DV will throw "...ClassNotFoundException: org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory". > Workaround: > Add "<module name="org.infinispan.client.hotrod"/>" as a dependency into module "org.jboss.teiid". -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2781) Unable to update database table with composite keys using OData

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2781?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2781: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1044746|https://bugzilla.redhat.com/show_bug.cgi?id=1044746] from MODIFIED to ON_QA > Unable to update database table with composite keys using OData > --------------------------------------------------------------- > > Key: TEIID-2781 > URL: https://issues.jboss.org/browse/TEIID-2781 > Project: Teiid > Issue Type: Bug > Components: SOAP Services > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.7 > > Attachments: odataerror.txt, post-screen-shot.png, Shell00990083.tar > > > Using Postgres db, and created a table with composite keys. > CREATE TABLE composite_key > ( > ou_id character varying(3) NOT NULL, > product_name character varying(15) NOT NULL, > product_price numeric(10,2), > CONSTRAINT composite_key_pkey PRIMARY KEY (ou_id, product_name) > ) > WITH ( > OIDS=FALSE > ); > ALTER TABLE composite_key OWNER TO postgres; > INSERT INTO composite_key VALUES ('1','1',1); > INSERT INTO composite_key VALUES ('1','2',1.20); > INSERT INTO composite_key VALUES ('2','1',2.10); > Deploy the VDB and use SOAP UI to do PUT (aka SQL UPDATE) generates attached odataerror.txt -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2802) HIVE2: got Invalid table alias or column reference when running UNION ALL query on HIVE2

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2802?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2802: ------------------------------------- https://cwiki.apache.org/confluence/display/Hive/LanguageManual+SubQueries > HIVE2: got Invalid table alias or column reference when running UNION ALL query on HIVE2 > ----------------------------------------------------------------------------------------- > > Key: TEIID-2802 > URL: https://issues.jboss.org/browse/TEIID-2802 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.6 > Environment: TEIID with HIVE2 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: teiid > > If I tried to combine 2 tables from a same HIVE2 data source using UNION ALL, I got "Invalid table alias or column reference" error. > Query that I submitted to Teiid originally: > select "name" > from (Select * from hive2.opportunities_small UNION ALL Select * from > hive2.opportunities) "query" > group by "name" > order by "name" > Query that Teiid generated: > SELECT v_0.c_0 FROM (SELECT c_0 FROM (SELECT g_1.name AS c_0 FROM > opportunities_small g_1 UNION ALL SELECT g_0.name AS c_0 FROM opportunities > g_0) X__) v_0 GROUP BY v_0.c_0 ORDER BY v_0.c_0 > Error: > Invalid table alias or column reference 'v_0': (possible column names are: c_0) -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2802) HIVE2: got Invalid table alias or column reference when running UNION ALL query on HIVE2

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2802?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2802: --------------------------------------- Does hive support inline views? > HIVE2: got Invalid table alias or column reference when running UNION ALL query on HIVE2 > ----------------------------------------------------------------------------------------- > > Key: TEIID-2802 > URL: https://issues.jboss.org/browse/TEIID-2802 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.6 > Environment: TEIID with HIVE2 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: teiid > > If I tried to combine 2 tables from a same HIVE2 data source using UNION ALL, I got "Invalid table alias or column reference" error. > Query that I submitted to Teiid originally: > select "name" > from (Select * from hive2.opportunities_small UNION ALL Select * from > hive2.opportunities) "query" > group by "name" > order by "name" > Query that Teiid generated: > SELECT v_0.c_0 FROM (SELECT c_0 FROM (SELECT g_1.name AS c_0 FROM > opportunities_small g_1 UNION ALL SELECT g_0.name AS c_0 FROM opportunities > g_0) X__) v_0 GROUP BY v_0.c_0 ORDER BY v_0.c_0 > Error: > Invalid table alias or column reference 'v_0': (possible column names are: c_0) -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2802) HIVE2: got Invalid table alias or column reference when running UNION ALL query on HIVE2

by Ivan Chan (JIRA)

Ivan Chan created TEIID-2802: -------------------------------- Summary: HIVE2: got Invalid table alias or column reference when running UNION ALL query on HIVE2 Key: TEIID-2802 URL: https://issues.jboss.org/browse/TEIID-2802 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.6 Environment: TEIID with HIVE2 Reporter: Ivan Chan Assignee: Steven Hawkins If I tried to combine 2 tables from a same HIVE2 data source using UNION ALL, I got "Invalid table alias or column reference" error. Query that I submitted to Teiid originally: select "name" from (Select * from hive2.opportunities_small UNION ALL Select * from hive2.opportunities) "query" group by "name" order by "name" Query that Teiid generated: SELECT v_0.c_0 FROM (SELECT c_0 FROM (SELECT g_1.name AS c_0 FROM opportunities_small g_1 UNION ALL SELECT g_0.name AS c_0 FROM opportunities g_0) X__) v_0 GROUP BY v_0.c_0 ORDER BY v_0.c_0 Error: Invalid table alias or column reference 'v_0': (possible column names are: c_0) -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2801) HIVE2: HAVING specified without GROUP BY

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2801?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2801: --------------------------------------- There are two parts here. The first is to double check the aggregate pushdown logic to see if we really need the null check in this and similar cases. The other is that we don't currently have a way for capabilities to convey that having requires group by. > HIVE2: HAVING specified without GROUP BY > ----------------------------------------- > > Key: TEIID-2801 > URL: https://issues.jboss.org/browse/TEIID-2801 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.6 > Environment: Teiid with HIVE1 and HIVE2 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: teiid > > If SQL contains HAVING, with group by. > HIVE2 will throw the following exception: > HAVING specified without GROUP BY, errorCode:40000, SQLState:42000) > at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1494) > at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1480) > at org.apache.hadoop.hive.service.ThriftHive$execute_result.read(ThriftHive.java:1430) > at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78) > at org.apache.hadoop.hive.service.ThriftHive$Client.recv_execute(ThriftHive.java:116) > at org.apache.hadoop.hive.service.ThriftHive$Client.execute(ThriftHive.java:103) > at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeImmediate(HivePreparedStatement.java:175) -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2801) HIVE2: HAVING specified without GROUP BY

by Ivan Chan (JIRA)

Ivan Chan created TEIID-2801: -------------------------------- Summary: HIVE2: HAVING specified without GROUP BY Key: TEIID-2801 URL: https://issues.jboss.org/browse/TEIID-2801 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.6 Environment: Teiid with HIVE1 and HIVE2 Reporter: Ivan Chan Assignee: Steven Hawkins If SQL contains HAVING, with group by. HIVE2 will throw the following exception: HAVING specified without GROUP BY, errorCode:40000, SQLState:42000) at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1494) at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1480) at org.apache.hadoop.hive.service.ThriftHive$execute_result.read(ThriftHive.java:1430) at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78) at org.apache.hadoop.hive.service.ThriftHive$Client.recv_execute(ThriftHive.java:116) at org.apache.hadoop.hive.service.ThriftHive$Client.execute(ThriftHive.java:103) at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeImmediate(HivePreparedStatement.java:175) -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2799) Import metadata from Object translator is not defining primary key

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2799?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2799: ---------------------------------- Fix Version/s: 8.7 > Import metadata from Object translator is not defining primary key > ------------------------------------------------------------------ > > Key: TEIID-2799 > URL: https://issues.jboss.org/browse/TEIID-2799 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 8.7 > > > The infinispan implementation of the object translator getMetadata is not defining the primary key. If the resource-adapter has defined it, it should expose it. This key is important for push-down capability. The user could define this after the fact (i.e, in dynamic vdb or in designer), but from a usability stand point, it would be better if the translator exposed it. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2458) Sybase15 subquery using HAVING clause failing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2458?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2458: ------------------------------------------------ Filip Nguyen <fnguyen(a)redhat.com> changed the Status of [bug 996550|https://bugzilla.redhat.com/show_bug.cgi?id=996550] from ON_QA to VERIFIED > Sybase15 subquery using HAVING clause failing > --------------------------------------------- > > Key: TEIID-2458 > URL: https://issues.jboss.org/browse/TEIID-2458 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Example query is failing: SELECT INTKEY, STRINGKEY, FLOATNUM FROM BQT1.SMALLA GROUP BY INTKEY, STRINGKEY, FLOATNUM HAVING FLOATNUM = (SELECT FLOATNUM FROM BQT1.SMALLA WHERE STRINGKEY = 20) > When this query is submitted through EDS using Squirrel or BQT as a client it returns: > IntKey StringKey > 20 20 0 > When the resulting source-specific query generated from EDS is submitted direct to Sybase15 the same results are returned. > SELECT g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real) FROM SmallA g_0 WHERE cast(g_0.FloatNum AS real) = (SELECT cast(g_1.FloatNum AS real) FROM SmallA g_1 WHERE g_1.StringKey = '20') GROUP BY g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real)is submitted direct to Sybase15 > RESULTS > IntKey StringKey > 20 20 0 > However, when the GROUP BY is removed from the query it returns the expected results as shown below: > IntKey StringKey > 20 20 -4 > The supporting VDB can be provided if needed. -- 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

12 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2014