January 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5190) Postgresql translator does not support expressions in group by

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5190?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5190: --------------------------------------- Thanks [~inoshg]. Also added to 10.0.3 for continuity. > Postgresql translator does not support expressions in group by > -------------------------------------------------------------- > > Key: TEIID-5190 > URL: https://issues.jboss.org/browse/TEIID-5190 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.1, 9.3.6, 10.0.3 > > > Inline views are being added in situations involving expressions in the group by clause because the translator is not marked as supporting that. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5190) Postgresql translator does not support expressions in group by

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5190?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5190: ---------------------------------- Fix Version/s: 10.0.3 9.3.6 > Postgresql translator does not support expressions in group by > -------------------------------------------------------------- > > Key: TEIID-5190 > URL: https://issues.jboss.org/browse/TEIID-5190 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.1, 9.3.6, 10.0.3 > > > Inline views are being added in situations involving expressions in the group by clause because the translator is not marked as supporting that. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5067) Incorrect source query with simple inherent updates

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5067?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-5067: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1491374|https://bugzilla.redhat.com/show_bug.cgi?id=1491374] from ON_QA to VERIFIED > Incorrect source query with simple inherent updates > --------------------------------------------------- > > Key: TEIID-5067 > URL: https://issues.jboss.org/browse/TEIID-5067 > Project: Teiid > Issue Type: Bug > Components: JDG Connector, Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Critical > Fix For: 10.0, 8.12.x-6.4, 9.2.6, 9.3.4 > > > A delete query against a view fails, when in WHERE clause there is a filter on non-directly mapped column. Please note, that the integer type is only example, this happens for any type (time/date/timestamp amongst other). > {code} > CREATE FOREIGN TABLE SmallA ( > IntValue string, > StringKey string PRIMARY KEY > ) OPTIONS(UPDATABLE true); > CREATE VIEW VSmallA( > IntValue integer, > StringKey string PRIMARY KEY > ) OPTIONS (UPDATABLE true) AS > SELECT > CONVERT(source.IntValue,integer), source.StringKey FROM Source.SmallA as source; > {code} > And following queries: > {code:sql|title=DELETE query} > DELETE FROM VSmallA WHERE IntValue=13 > UPDATE VSmallA Set StringKey='a' WHERE IntValue=13 > {code} > I get an incorrect source query with x.intvalue in the predicate. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5201) Update teiid pg_type schema to match PostgreSQL pg_type in support of NPGsql provider

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5201?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5201: --------------------------------------- Yes, it should be built over the weekend. > Update teiid pg_type schema to match PostgreSQL pg_type in support of NPGsql provider > ------------------------------------------------------------------------------------- > > Key: TEIID-5201 > URL: https://issues.jboss.org/browse/TEIID-5201 > Project: Teiid > Issue Type: Bug > Components: ODBC, Query Engine > Reporter: Divyesh Vallabh > Assignee: Steven Hawkins > > When using NpgSQL provider to connect to Teiid the connection fails because the teiid.pg_type table does not contain the column "typreceive" > Add missing columns from Postgres.pg_type (https://www.postgresql.org/docs/9.2/static/catalog-pg-type.html) to teiid > Add missing columns from Postgres.pg_user (https://www.postgresql.org/docs/9.2/static/view-pg-user.html) to teiid > Add missing columns from Postgres.pg_constraint (https://www.postgresql.org/docs/9.2/static/catalog-pg-constraint.html) to teiid -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5201) Update teiid pg_type schema to match PostgreSQL pg_type in support of NPGsql provider

by Divyesh Vallabh (JIRA)

[ https://issues.jboss.org/browse/TEIID-5201?page=com.atlassian.jira.plugin... ] Divyesh Vallabh commented on TEIID-5201: ---------------------------------------- Yes, will test it out next week. Will the latest snapshot link be available on (http://teiid.jboss.org/downloads/) > Update teiid pg_type schema to match PostgreSQL pg_type in support of NPGsql provider > ------------------------------------------------------------------------------------- > > Key: TEIID-5201 > URL: https://issues.jboss.org/browse/TEIID-5201 > Project: Teiid > Issue Type: Bug > Components: ODBC, Query Engine > Reporter: Divyesh Vallabh > Assignee: Steven Hawkins > > When using NpgSQL provider to connect to Teiid the connection fails because the teiid.pg_type table does not contain the column "typreceive" > Add missing columns from Postgres.pg_type (https://www.postgresql.org/docs/9.2/static/catalog-pg-type.html) to teiid > Add missing columns from Postgres.pg_user (https://www.postgresql.org/docs/9.2/static/view-pg-user.html) to teiid > Add missing columns from Postgres.pg_constraint (https://www.postgresql.org/docs/9.2/static/catalog-pg-constraint.html) to teiid -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5201) Update teiid pg_type schema to match PostgreSQL pg_type in support of NPGsql provider

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5201?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5201: --------------------------------------- The initial changes for this are in. [~dvallabh_doi] can you build locally or pick up the latest snapshot next week to test this? > Update teiid pg_type schema to match PostgreSQL pg_type in support of NPGsql provider > ------------------------------------------------------------------------------------- > > Key: TEIID-5201 > URL: https://issues.jboss.org/browse/TEIID-5201 > Project: Teiid > Issue Type: Bug > Components: ODBC, Query Engine > Reporter: Divyesh Vallabh > Assignee: Steven Hawkins > > When using NpgSQL provider to connect to Teiid the connection fails because the teiid.pg_type table does not contain the column "typreceive" > Add missing columns from Postgres.pg_type (https://www.postgresql.org/docs/9.2/static/catalog-pg-type.html) to teiid > Add missing columns from Postgres.pg_user (https://www.postgresql.org/docs/9.2/static/view-pg-user.html) to teiid > Add missing columns from Postgres.pg_constraint (https://www.postgresql.org/docs/9.2/static/catalog-pg-constraint.html) to teiid -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4679) PrestoDB translator - locate function - source specific function has different order of arguments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4679?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4679: ------------------------------------------------ David Le Sage <dlesage(a)redhat.com> changed the Status of [bug 1456401|https://bugzilla.redhat.com/show_bug.cgi?id=1456401] from ASSIGNED to ON_QA > PrestoDB translator - locate function - source specific function has different order of arguments > ------------------------------------------------------------------------------------------------- > > Key: TEIID-4679 > URL: https://issues.jboss.org/browse/TEIID-4679 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.8.6_3 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 9.2, 9.1.3 > > > For PrestoDB translator, *locate(x,y)* is translated as *strpos(x,y)* - i.e. *strpos(substring, string)*, but function has different order of arguments - from [PrestoDB documentation|https://prestodb.io/docs/current/functions/string.html] - *strpos(string, substring)* > {code:sql|title=Query} > SELECT StringNum, LOCATE('1', StringNum) FROM BQT1.SmallA > {code} > {code:sql|title=Source-specific command} > SELECT g_0.stringnum, strpos('1', g_0.stringnum) FROM smalla AS g_0 > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5159) Quickstart hibernate-on-top-of-teiid usability issues

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5159?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-5159: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1514849|https://bugzilla.redhat.com/show_bug.cgi?id=1514849] from ON_QA to VERIFIED > Quickstart hibernate-on-top-of-teiid usability issues > ----------------------------------------------------- > > Key: TEIID-5159 > URL: https://issues.jboss.org/browse/TEIID-5159 > Project: Teiid > Issue Type: Bug > Components: Quick Starts > Affects Versions: 8.12.x-6.4 > Reporter: Jan Stastny > Assignee: Van Halbert > Fix For: 8.12.x-6.4, 10.x > > > There are two usability issues: > 1. we're reusing Portfolio vdb. The thing is, that if user performed also dynamicvdb-dataroles quickstart, the Portfolio vdb will have limitations on data access. So it is crucial, for the functionality of hibernate qs for user to provide correct credentials. It has to be credentials allowing read access for the example query in the end. > 2. mvn package is enough, no need for mvn install when building WAR file -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5193) Osisoft translator - correlated subquery on HAVING clause fails

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5193?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5193: ---------------------------------- Fix Version/s: (was: 8.12.x-6.4) > Osisoft translator - correlated subquery on HAVING clause fails > --------------------------------------------------------------- > > Key: TEIID-5193 > URL: https://issues.jboss.org/browse/TEIID-5193 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.x-6.4 > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Fix For: 10.1 > > > Running a query with a correlated subquery in a HAVING clause, such as > {code:sql} > SELECT INTKEY, STRINGKEY > FROM BQT1.SMALLA AS A > WHERE NOT (INTKEY IN (10)) > GROUP BY INTKEY, STRINGKEY > HAVING INTKEY = (SELECT MIN(STRINGKEY) FROM BQT1.SMALLA AS B WHERE A.INTKEY = B.INTKEY) > {code} > fails on the datasource with > bq. com.osisoft.rdsa.RdsaException: [PIOLEDBENT] HAVING condition cannot be nonaggregate. > This seems to be an issue on the Osisoft PI datasource side, as running the query directly against the datasource produces the same failure. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5193) Osisoft translator - correlated subquery on HAVING clause fails

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5193?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5193: ------------------------------------ If you don't think this is applicable to the 64 branch, then the PR can be closed it guess. > Osisoft translator - correlated subquery on HAVING clause fails > --------------------------------------------------------------- > > Key: TEIID-5193 > URL: https://issues.jboss.org/browse/TEIID-5193 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.x-6.4 > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Fix For: 8.12.x-6.4, 10.1 > > > Running a query with a correlated subquery in a HAVING clause, such as > {code:sql} > SELECT INTKEY, STRINGKEY > FROM BQT1.SMALLA AS A > WHERE NOT (INTKEY IN (10)) > GROUP BY INTKEY, STRINGKEY > HAVING INTKEY = (SELECT MIN(STRINGKEY) FROM BQT1.SMALLA AS B WHERE A.INTKEY = B.INTKEY) > {code} > fails on the datasource with > bq. com.osisoft.rdsa.RdsaException: [PIOLEDBENT] HAVING condition cannot be nonaggregate. > This seems to be an issue on the Osisoft PI datasource side, as running the query directly against the datasource produces the same failure. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018