April 2018 - teiid-issues - Jboss List Archives

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

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5319?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5319: --------------------------------- Fix Version/s: 8.12.13.6_4 > 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 > Fix For: 10.3, 10.2.1, 8.12.13.6_4, 10.1.4 > > > 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-5320) SAP IQ translator wrong pushdown of dateadd function

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5320?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5320: --------------------------------- Fix Version/s: 8.12.13.6_4 > 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 > Fix For: 10.3, 10.2.1, 8.12.13.6_4 > > > 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 Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5319?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5319. ----------------------------------- Fix Version/s: 10.1.4 10.3 10.2.1 Resolution: Done Added the useParensForJoins option. > 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 > Fix For: 10.1.4, 10.3, 10.2.1 > > > 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-5322) create public ci

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5322?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5322: ---------------------------------- Fix Version/s: 10.3 > create public ci > ---------------- > > Key: TEIID-5322 > URL: https://issues.jboss.org/browse/TEIID-5322 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.3 > > > Now that jboss public hudson has been decommissioned our jenkins build is fully private. We should promote a public ci build. > At least travis had issues with the size of the build log: https://docs.travis-ci.com/user/common-build-problems/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5323) info logging of commands is too high by default for teiid embedded

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5323: ------------------------------------- Summary: info logging of commands is too high by default for teiid embedded Key: TEIID-5323 URL: https://issues.jboss.org/browse/TEIID-5323 Project: Teiid Issue Type: Task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.3 >From TEIID-5007 we had not resolved: Another issue that affects non-Wildfly usage are the defaults for command logging. For backwards compatibility the splitting of logging source/user level queries means that the user queries are logged at an info level - this may be too verbose. We could introduce a breaking/configurable change to alter this behavior. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5322) create public ci

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5322: ------------------------------------- Summary: create public ci Key: TEIID-5322 URL: https://issues.jboss.org/browse/TEIID-5322 Project: Teiid Issue Type: Task Components: Build/Kits Reporter: Steven Hawkins Assignee: Steven Hawkins Now that jboss public hudson has been decommissioned our jenkins build is fully private. We should promote a public ci build. At least travis had issues with the size of the build log: https://docs.travis-ci.com/user/common-build-problems/ -- 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)

[ https://issues.jboss.org/browse/TEIID-5319?page=com.atlassian.jira.plugin... ] Jan Stastny commented on TEIID-5319: ------------------------------------ [~shawkins] Yes, the parentheses are needed, the original error I am getting for the actually pushed source cmd: {code} Error: SQL Anywhere Error -131: Syntax error near 'ON' on line 8 SQLState: 42W04 ErrorCode: 102 {code} The issue is two ON statements in succession. > 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-5321) SAP IQ numeric functions corner case differences

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5321?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5321: ---------------------------------- Fix Version/s: 10.x > SAP IQ numeric functions corner case differences > ------------------------------------------------ > > Key: TEIID-5321 > URL: https://issues.jboss.org/browse/TEIID-5321 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.13.6_4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Priority: Minor > Fix For: 10.x > > > The following discrepancies in return values of numeric functions are caused by SAP IQ's behaviour. > # COT(0) > #* results in OutOfRange error in Teiid > #* returns NULL in SAP IQ > # EXP\(n\) - for n < -15 > #* result is 0 in Teiid > #* result is in SAP IQ > #** 0 for -15 > n >=-745 > #** NULL for n<=-746 -- 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 Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5320?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5320. ----------------------------------- Fix Version/s: 10.3 10.2.1 Resolution: Done Updated the modify to output the part as a literal or as a keyword. > 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 > Fix For: 10.3, 10.2.1 > > > 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-5321) SAP IQ numeric functions corner case differences

by Jan Stastny (JIRA)

Jan Stastny created TEIID-5321: ---------------------------------- Summary: SAP IQ numeric functions corner case differences Key: TEIID-5321 URL: https://issues.jboss.org/browse/TEIID-5321 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.12.13.6_4 Reporter: Jan Stastny Assignee: Steven Hawkins Priority: Minor The following discrepancies in return values of numeric functions are caused by SAP IQ's behaviour. # COT(0) #* results in OutOfRange error in Teiid #* returns NULL in SAP IQ # EXP\(n\) - for n < -15 #* result is 0 in Teiid #* result is in SAP IQ #** 0 for -15 > n >=-745 #** NULL for n<=-746 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2018