April 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5317) Add support for ODBC 3.0 functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5317?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5317. ----------------------------------- Fix Version/s: 10.3 Resolution: Done Added current_date(), current_time[(precision)], and current_timestamp[(precision)] to Teiid. To conform to our expectations the current_time precision is ignored. We also only get the current_timestamp to at most millisecond resolution. > Add support for ODBC 3.0 functions > ---------------------------------- > > Key: TEIID-5317 > URL: https://issues.jboss.org/browse/TEIID-5317 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.12.12.6_4 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 10.3 > > > Looking to add support for ODBC 3 functions like "CURRENT_TIMESTAMP" and "CURRENT_DATE()" as indicated in linke [1]. This would be in support of applications that auto-generate backend SQL such as Tableau or Spotfire. > [1] https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/time-date-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5319) SAP IQ translator wrong pushdown of query with multiple JOINs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5319?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5319: --------------------------------------- The teiid syntax is generally valid and seems allowable given https://help.sap.com/viewer/a898e08b84f21015969fa437e89860c8/16.1.3.0/en-... What is the parsing error you are seeing? Can you see if directly issuing the source query with nesting parens works? {code} SELECT g_1."intkey" AS c_0, g_2."intkey" AS c_1, g_0."intkey" AS c_2 FROM "bqt-server"."dvqe"."LargeB" AS g_0 LEFT OUTER JOIN ("bqt-server"."dvqe"."SmallA" AS g_1 INNER JOIN "bqt-server"."dvqe"."MediumB" AS g_2 ON g_1."intkey" = g_2."intkey") ON g_2."intkey" = g_0."intkey" AND g_2."intkey" < 1500 WHERE g_0."intkey" < 1500 {code} > SAP IQ translator wrong pushdown of query with multiple JOINs > ------------------------------------------------------------- > > Key: TEIID-5319 > URL: https://issues.jboss.org/browse/TEIID-5319 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.13.6_4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Critical > > For a query: > {code:sql} > SELECT BQT1.SmallA.IntKey AS SmallA_IntKey, BQT2.MediumB.IntKey AS MediumB_IntKey, BQT2.LargeB.IntKey AS LargeB_IntKey > FROM > ( > BQT1.SmallA LEFT OUTER JOIN BQT2.MediumB > ON BQT1.SmallA.IntKey = BQT2.MediumB.IntKey > ) > RIGHT OUTER JOIN BQT2.LargeB > ON BQT2.MediumB.IntKey = BQT2.LargeB.IntKey > WHERE BQT2.LargeB.IntKey < 1500 > {code} > The following source command is pushed to SAP IQ: > {code:sql} > SELECT g_1."intkey" AS c_0, g_2."intkey" AS c_1, g_0."intkey" AS c_2 > FROM > "bqt-server"."dvqe"."LargeB" AS g_0 > LEFT OUTER JOIN > "bqt-server"."dvqe"."SmallA" AS g_1 > INNER JOIN "bqt-server"."dvqe"."MediumB" AS g_2 > ON g_1."intkey" = g_2."intkey" > ON g_2."intkey" = g_0."intkey" > AND g_2."intkey" < 1500 > WHERE g_0."intkey" < 1500 > {code} > Which results in parsing error. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5319) SAP IQ translator wrong pushdown of query with multiple JOINs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5319?page=com.atlassian.jira.plugin... ] Work on TEIID-5319 started by Steven Hawkins. --------------------------------------------- > SAP IQ translator wrong pushdown of query with multiple JOINs > ------------------------------------------------------------- > > Key: TEIID-5319 > URL: https://issues.jboss.org/browse/TEIID-5319 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.13.6_4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Critical > > For a query: > {code:sql} > SELECT BQT1.SmallA.IntKey AS SmallA_IntKey, BQT2.MediumB.IntKey AS MediumB_IntKey, BQT2.LargeB.IntKey AS LargeB_IntKey > FROM > ( > BQT1.SmallA LEFT OUTER JOIN BQT2.MediumB > ON BQT1.SmallA.IntKey = BQT2.MediumB.IntKey > ) > RIGHT OUTER JOIN BQT2.LargeB > ON BQT2.MediumB.IntKey = BQT2.LargeB.IntKey > WHERE BQT2.LargeB.IntKey < 1500 > {code} > The following source command is pushed to SAP IQ: > {code:sql} > SELECT g_1."intkey" AS c_0, g_2."intkey" AS c_1, g_0."intkey" AS c_2 > FROM > "bqt-server"."dvqe"."LargeB" AS g_0 > LEFT OUTER JOIN > "bqt-server"."dvqe"."SmallA" AS g_1 > INNER JOIN "bqt-server"."dvqe"."MediumB" AS g_2 > ON g_1."intkey" = g_2."intkey" > ON g_2."intkey" = g_0."intkey" > AND g_2."intkey" < 1500 > WHERE g_0."intkey" < 1500 > {code} > Which results in parsing error. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4646) Add engine support for lead/lag aggregate functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4646?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4646: --------------------------------------- [~jolee] no they were added with this jira - it's in the description, but no the title. > Add engine support for lead/lag aggregate functions > --------------------------------------------------- > > Key: TEIID-4646 > URL: https://issues.jboss.org/browse/TEIID-4646 > Project: Teiid > Issue Type: Enhancement > Components: Grammar, JDBC Connector, Misc. Connectors, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3, 8.12.13.6_4 > > > Lead/lag and first_value/last_value analytical function support should be added to the engine with appropriate pushdown support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5320) SAP IQ translator wrong pushdown of dateadd function

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5320?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-5320: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1569538 Bugzilla Update: Perform > SAP IQ translator wrong pushdown of dateadd function > ---------------------------------------------------- > > Key: TEIID-5320 > URL: https://issues.jboss.org/browse/TEIID-5320 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.13.6_4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > > SAP IQ translator's pushdown of DATEADD function is wrong. > The function DATEADD has following signature in SAP IQ: > bq. DATEADD ( date-part, numeric-expression, date-expression ) > the date-part is of type Date Part, see (1). > Teiid is currently pushing DATEADD function with date-part argument as string, which causes an error. It should be Date Part identifier, e.g. instead of 'DAY', it should be DAY. > (1) http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5320) SAP IQ translator wrong pushdown of dateadd function

by Jan Stastny (JIRA)

Jan Stastny created TEIID-5320: ---------------------------------- Summary: SAP IQ translator wrong pushdown of dateadd function Key: TEIID-5320 URL: https://issues.jboss.org/browse/TEIID-5320 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.12.13.6_4 Reporter: Jan Stastny Assignee: Steven Hawkins SAP IQ translator's pushdown of DATEADD function is wrong. The function DATEADD has following signature in SAP IQ: bq. DATEADD ( date-part, numeric-expression, date-expression ) the date-part is of type Date Part, see (1). Teiid is currently pushing DATEADD function with date-part argument as string, which causes an error. It should be Date Part identifier, e.g. instead of 'DAY', it should be DAY. (1) http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5319) SAP IQ translator wrong pushdown of query with multiple JOINs

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5319?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-5319: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1569509 Bugzilla Update: Perform > SAP IQ translator wrong pushdown of query with multiple JOINs > ------------------------------------------------------------- > > Key: TEIID-5319 > URL: https://issues.jboss.org/browse/TEIID-5319 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.13.6_4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Critical > > For a query: > {code:sql} > SELECT BQT1.SmallA.IntKey AS SmallA_IntKey, BQT2.MediumB.IntKey AS MediumB_IntKey, BQT2.LargeB.IntKey AS LargeB_IntKey > FROM > ( > BQT1.SmallA LEFT OUTER JOIN BQT2.MediumB > ON BQT1.SmallA.IntKey = BQT2.MediumB.IntKey > ) > RIGHT OUTER JOIN BQT2.LargeB > ON BQT2.MediumB.IntKey = BQT2.LargeB.IntKey > WHERE BQT2.LargeB.IntKey < 1500 > {code} > The following source command is pushed to SAP IQ: > {code:sql} > SELECT g_1."intkey" AS c_0, g_2."intkey" AS c_1, g_0."intkey" AS c_2 > FROM > "bqt-server"."dvqe"."LargeB" AS g_0 > LEFT OUTER JOIN > "bqt-server"."dvqe"."SmallA" AS g_1 > INNER JOIN "bqt-server"."dvqe"."MediumB" AS g_2 > ON g_1."intkey" = g_2."intkey" > ON g_2."intkey" = g_0."intkey" > AND g_2."intkey" < 1500 > WHERE g_0."intkey" < 1500 > {code} > Which results in parsing error. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5319) SAP IQ translator wrong pushdown of query with multiple JOINs

by Jan Stastny (JIRA)

Jan Stastny created TEIID-5319: ---------------------------------- Summary: SAP IQ translator wrong pushdown of query with multiple JOINs Key: TEIID-5319 URL: https://issues.jboss.org/browse/TEIID-5319 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.12.13.6_4 Reporter: Jan Stastny Assignee: Steven Hawkins Priority: Critical For a query: {code:sql} SELECT BQT1.SmallA.IntKey AS SmallA_IntKey, BQT2.MediumB.IntKey AS MediumB_IntKey, BQT2.LargeB.IntKey AS LargeB_IntKey FROM ( BQT1.SmallA LEFT OUTER JOIN BQT2.MediumB ON BQT1.SmallA.IntKey = BQT2.MediumB.IntKey ) RIGHT OUTER JOIN BQT2.LargeB ON BQT2.MediumB.IntKey = BQT2.LargeB.IntKey WHERE BQT2.LargeB.IntKey < 1500 {code} The following source command is pushed to SAP IQ: {code:sql} SELECT g_1."intkey" AS c_0, g_2."intkey" AS c_1, g_0."intkey" AS c_2 FROM "bqt-server"."dvqe"."LargeB" AS g_0 LEFT OUTER JOIN "bqt-server"."dvqe"."SmallA" AS g_1 INNER JOIN "bqt-server"."dvqe"."MediumB" AS g_2 ON g_1."intkey" = g_2."intkey" ON g_2."intkey" = g_0."intkey" AND g_2."intkey" < 1500 WHERE g_0."intkey" < 1500 {code} Which results in parsing error. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5314) usage of environment properties

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5314?page=com.atlassian.jira.plugin... ] Work on TEIID-5314 started by Steven Hawkins. --------------------------------------------- > usage of environment properties > ------------------------------- > > Key: TEIID-5314 > URL: https://issues.jboss.org/browse/TEIID-5314 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.3 > > > Places in Teiid that look for system properties should allow for overrides to be specified via environment properties as well. This will make it easier to configure optional behavior on openshift. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5317) Add support for ODBC 3.0 functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5317?page=com.atlassian.jira.plugin... ] Work on TEIID-5317 started by Steven Hawkins. --------------------------------------------- > Add support for ODBC 3.0 functions > ---------------------------------- > > Key: TEIID-5317 > URL: https://issues.jboss.org/browse/TEIID-5317 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.12.12.6_4 > Reporter: Marc Shirley > Assignee: Steven Hawkins > > Looking to add support for ODBC 3 functions like "CURRENT_TIMESTAMP" and "CURRENT_DATE()" as indicated in linke [1]. This would be in support of applications that auto-generate backend SQL such as Tableau or Spotfire. > [1] https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/time-date-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2018