October 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5112) Add parsing restrictions for 0 length

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5112: ------------------------------------- Summary: Add parsing restrictions for 0 length Key: TEIID-5112 URL: https://issues.jboss.org/browse/TEIID-5112 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Related to TEIID-5111 the parser and other logic should ensure that length of 0 is not allowed in ddl as a length value. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5111) Teiid Designer uses 0 as a default length value

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5111: ------------------------------------- Summary: Teiid Designer uses 0 as a default length value Key: TEIID-5111 URL: https://issues.jboss.org/browse/TEIID-5111 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 8.12 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.0 If you create a view in teiid designer, but define it with an expression: select case when rand() < .5 then 'heads' else 'tails' end as x A string column length will be set to 0. On the server this may cause issues such as with the odata layer that will check facets against the length of 0. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5110) Set operations and parenthesis

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5110: ------------------------------------- Summary: Set operations and parenthesis Key: TEIID-5110 URL: https://issues.jboss.org/browse/TEIID-5110 Project: Teiid Issue Type: Bug Components: Connector API, Query Engine Reporter: Mike Higgins Assignee: Steven Hawkins Priority: Blocker Fix For: 10.0, 9.3.4, 9.2.7 Using Teiid 9.2.2 with postgresql, I issue a query structured like this: (a UNION ALL b UNION ALL c) INTERSECT d All queries are from a single database. This query does not give back the expected result. In the plan, I see the query printed with no parenthesis around the unions: a UNION ALL b UNION ALL c INTERSECT d This gives the same result as the query submitted with no parens in it (the intersect of c and d is unioned with a union b. The expepeted result is to preserve the paren so that the intersect is performed against the union of all three tables. As a note, using UNION instead of UNION ALL did not preserve the parens, either. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5109) Set operations and parenthesis

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5109?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5109. ----------------------------------- Resolution: Done Updated the logic to allow both nested queries on the left to consider intersect. > Set operations and parenthesis > ------------------------------ > > Key: TEIID-5109 > URL: https://issues.jboss.org/browse/TEIID-5109 > Project: Teiid > Issue Type: Bug > Components: Connector API, Query Engine > Reporter: Mike Higgins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 10.0, 9.3.4, 9.2.7 > > > Using Teiid 9.2.2 with postgresql, I issue a query structured like this: > > (a > UNION ALL > b > UNION ALL > c) > INTERSECT > d > > All queries are from a single database. > This query does not give back the expected result. > In the plan, I see the query printed with no parenthesis around the unions: > a UNION ALL b UNION ALL c INTERSECT d > This gives the same result as the query submitted with no parens in it (the intersect of c and d is unioned with a union b. > The expepeted result is to preserve the paren so that the intersect is performed against the union of all three tables. > As a note, using UNION instead of UNION ALL did not preserve the parens, either. > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5109) Set operations and parenthesis

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5109?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5109: ---------------------------------- Component/s: Connector API Query Engine Fix Version/s: 10.0 9.3.4 9.2.7 Priority: Blocker (was: Major) > Set operations and parenthesis > ------------------------------ > > Key: TEIID-5109 > URL: https://issues.jboss.org/browse/TEIID-5109 > Project: Teiid > Issue Type: Bug > Components: Connector API, Query Engine > Reporter: Mike Higgins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 10.0, 9.3.4, 9.2.7 > > > Using Teiid 9.2.2 with postgresql, I issue a query structured like this: > > (a > UNION ALL > b > UNION ALL > c) > INTERSECT > d > > All queries are from a single database. > This query does not give back the expected result. > In the plan, I see the query printed with no parenthesis around the unions: > a UNION ALL b UNION ALL c INTERSECT d > This gives the same result as the query submitted with no parens in it (the intersect of c and d is unioned with a union b. > The expepeted result is to preserve the paren so that the intersect is performed against the union of all three tables. > As a note, using UNION instead of UNION ALL did not preserve the parens, either. > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5109) Set operations and parenthesis

by Mike Higgins (JIRA)

Mike Higgins created TEIID-5109: ----------------------------------- Summary: Set operations and parenthesis Key: TEIID-5109 URL: https://issues.jboss.org/browse/TEIID-5109 Project: Teiid Issue Type: Bug Reporter: Mike Higgins Assignee: Steven Hawkins Using Teiid 9.2.2 with postgresql, I issue a query structured like this: (a UNION ALL b UNION ALL c) INTERSECT d All queries are from a single database. This query does not give back the expected result. In the plan, I see the query printed with no parenthesis around the unions: a UNION ALL b UNION ALL c INTERSECT d This gives the same result as the query submitted with no parens in it (the intersect of c and d is unioned with a union b. The expepeted result is to preserve the paren so that the intersect is performed against the union of all three tables. As a note, using UNION instead of UNION ALL did not preserve the parens, either. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4870) Google translator unexpected behavior for view update without trigger

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4870?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4870. ----------------------------------- Resolution: Done Updated the logic to look for string column values in the rows to update and add a ' to the existing value. > Google translator unexpected behavior for view update without trigger > --------------------------------------------------------------------- > > Key: TEIID-4870 > URL: https://issues.jboss.org/browse/TEIID-4870 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Priority: Critical > Fix For: 10.0, 9.3.4, 9.2.7 > > Attachments: googlespreadsheetcrud-vdb.xml-direct-trig-up-orig > > > If there is a view (CRUD.SmallA_Direct) which defines only a subset of foreign table (Source.SmallA) columns, there needs to be defined a trigger for update to work correctly. Otherwise unexpected results are returned after executing update: > * for updated rows, it converts String columns of SmallA_Direct to decimal numbers, > * for not updated rows it returns null for String columns -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4870) Google translator unexpected behavior for view update without trigger

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4870?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4870: --------------------------------------- This appears to be another gdata related issue. When an update is issued against a row with existing data string values are implicitly converted to their matching automatic type. Even if the column has a fixed format and the update appears successful in the spreadsheet, the result still has what appears like null values. I'll see what I can do to workaround this. > Google translator unexpected behavior for view update without trigger > --------------------------------------------------------------------- > > Key: TEIID-4870 > URL: https://issues.jboss.org/browse/TEIID-4870 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Priority: Critical > Fix For: 10.0, 9.3.4, 9.2.7 > > Attachments: googlespreadsheetcrud-vdb.xml-direct-trig-up-orig > > > If there is a view (CRUD.SmallA_Direct) which defines only a subset of foreign table (Source.SmallA) columns, there needs to be defined a trigger for update to work correctly. Otherwise unexpected results are returned after executing update: > * for updated rows, it converts String columns of SmallA_Direct to decimal numbers, > * for not updated rows it returns null for String columns -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4870) Google translator unexpected behavior for view update without trigger

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4870?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4870: ---------------------------------- Component/s: Misc. Connectors Fix Version/s: 10.0 9.3.4 9.2.7 Priority: Critical (was: Major) > Google translator unexpected behavior for view update without trigger > --------------------------------------------------------------------- > > Key: TEIID-4870 > URL: https://issues.jboss.org/browse/TEIID-4870 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Priority: Critical > Fix For: 10.0, 9.3.4, 9.2.7 > > Attachments: googlespreadsheetcrud-vdb.xml-direct-trig-up-orig > > > If there is a view (CRUD.SmallA_Direct) which defines only a subset of foreign table (Source.SmallA) columns, there needs to be defined a trigger for update to work correctly. Otherwise unexpected results are returned after executing update: > * for updated rows, it converts String columns of SmallA_Direct to decimal numbers, > * for not updated rows it returns null for String columns -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4984) Support for netezza pushdown functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4984?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4984. ----------------------------------- Resolution: Done As there didn't seem to be a need for specific function support, this is being resolved as just adding support for pushdown of values/select without from. > Support for netezza pushdown functions > -------------------------------------- > > Key: TEIID-4984 > URL: https://issues.jboss.org/browse/TEIID-4984 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Affects Versions: 9.1.3 > Reporter: Kulbhushan Chaskar > Assignee: Steven Hawkins > Fix For: 10.0 > > > More information is available on link > https://developer.jboss.org/thread/275445 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2017