July 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3573) Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3573?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3573: ------------------------------------ The issue with changing SupportNot = False, is that the pushed down criteria is no longer done and end up doing table scans. The combination of intNum <> 23 and intNum is Null criteria is an issue in both cases. But in the first case where supportNot = TRUE, <null> values are returned in the result set when only specifying intNum <> 23. > Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values > ---------------------------------------------------------------------------- > > Key: TEIID-3573 > URL: https://issues.jboss.org/browse/TEIID-3573 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Filip Elias > Assignee: Van Halbert > > Operator '<>' returns true for NULL <> 1 > Example: > {code} > select intKey,intNum from smallA where intNum<>1 > {code} > It returns also rows which have NULL in column intNum > I believe that NULL <> 1 is not true in SQL. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3573) Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3573?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-3573 at 7/27/15 9:03 PM: ------------------------------------------------------------- Kept IsNull = false, changed supportNot = FALSE Query: select intKey,intNum from smallA where intNum <> 23 * teiid doesn't push down criteria and doesn't include the <null> value rows Query (adding Is Null): select intKey,intNum from smalla where intNum <> 23 and intNum is Null * no criteria pushed down, and returned no rows Query: select intKey,intNum, stringNum, floatnum from smalla where intNum Is Null * no criteria pushed down, and returns on the 4 rows that have <null> value Query: select intKey,intNum, stringNum, floatnum from smalla where intNum Is Not Null * returned the correct results was (Author: van.halbert): Kept IsNull = false, changed supportNot = FALSE Query: select intKey,intNum from smallA where intNum <> 23 * teiid doesn't push down criteria and doesn't include the <null> value rows Didn't need to test this query because of results above: (adding Is Null): select intKey,intNum from smalla where intNum <> 23 and intNum is Null Query: select intKey,intNum, stringNum, floatnum from smalla where intNum Is Null * no criteria pushed down, and returns on the 4 rows that have <null> value Query: select intKey,intNum, stringNum, floatnum from smalla where intNum Is Not Null * returned the correct results > Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values > ---------------------------------------------------------------------------- > > Key: TEIID-3573 > URL: https://issues.jboss.org/browse/TEIID-3573 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Filip Elias > Assignee: Van Halbert > > Operator '<>' returns true for NULL <> 1 > Example: > {code} > select intKey,intNum from smallA where intNum<>1 > {code} > It returns also rows which have NULL in column intNum > I believe that NULL <> 1 is not true in SQL. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3573) Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3573?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-3573 at 7/27/15 9:01 PM: ------------------------------------------------------------- I changed support for IsNULL to false. In the data, there are 4 rows that have <null> in the intNum column Query: select intKey,intNum from smallA where intNum <> 23 - teiid pushes the criteria down and <null> values are returned in the result set Query (adding Is Null): select intKey,intNum from smalla where intNum <> 23 and intNum is Null - teiid changes the criteria to WHERE 1 = 0 and returns no rows Query (adding Is Not Null): select intKey,intNum from smalla where intNum <> 23 and intNum is Not Null - teiid pushed down: WHERE g_0.intNum <> 23 and teiid handles the Not Null check, the results do not have the <null> values was (Author: van.halbert): I changed support for IsNULL to false. In the data, there are 4 rows that have <null> in the intNum column Query: select intKey,intNum from smallA where intKey <> 23 - teiid pushes the criteria down and <null> values are returned in the result set Query (adding Is Null): select intKey,intNum from smalla where intNum <> 23 and intNum is Null - teiid changes the criteria to WHERE 1 = 0 and returns no rows Query (adding Is Not Null): select intKey,intNum from smalla where intNum <> 23 and intNum is Not Null - teiid pushed down: WHERE g_0.intNum <> 23 and teiid handles the Not Null check, the results do not have the <null> values > Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values > ---------------------------------------------------------------------------- > > Key: TEIID-3573 > URL: https://issues.jboss.org/browse/TEIID-3573 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Filip Elias > Assignee: Van Halbert > > Operator '<>' returns true for NULL <> 1 > Example: > {code} > select intKey,intNum from smallA where intNum<>1 > {code} > It returns also rows which have NULL in column intNum > I believe that NULL <> 1 is not true in SQL. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3573) Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3573?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3573: ------------------------------------ Kept IsNull = false, changed supportNot = FALSE Query: select intKey,intNum from smallA where intNum <> 23 * teiid doesn't push down criteria and doesn't include the <null> value rows Didn't need to test this query because of results above: (adding Is Null): select intKey,intNum from smalla where intNum <> 23 and intNum is Null Query: select intKey,intNum, stringNum, floatnum from smalla where intNum Is Null * no criteria pushed down, and returns on the 4 rows that have <null> value Query: select intKey,intNum, stringNum, floatnum from smalla where intNum Is Not Null * returned the correct results > Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values > ---------------------------------------------------------------------------- > > Key: TEIID-3573 > URL: https://issues.jboss.org/browse/TEIID-3573 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Filip Elias > Assignee: Van Halbert > > Operator '<>' returns true for NULL <> 1 > Example: > {code} > select intKey,intNum from smallA where intNum<>1 > {code} > It returns also rows which have NULL in column intNum > I believe that NULL <> 1 is not true in SQL. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3573) Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3573?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3573: ------------------------------------ I changed support for IsNULL to false. In the data, there are 4 rows that have <null> in the intNum column Query: select intKey,intNum from smallA where intKey <> 23 - teiid pushes the criteria down and <null> values are returned in the result set Query (adding Is Null): select intKey,intNum from smalla where intNum <> 23 and intNum is Null - teiid changes the criteria to WHERE 1 = 0 and returns no rows Query (adding Is Not Null): select intKey,intNum from smalla where intNum <> 23 and intNum is Not Null - teiid pushed down: WHERE g_0.intNum <> 23 and teiid handles the Not Null check, the results do not have the <null> values > Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values > ---------------------------------------------------------------------------- > > Key: TEIID-3573 > URL: https://issues.jboss.org/browse/TEIID-3573 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Filip Elias > Assignee: Van Halbert > > Operator '<>' returns true for NULL <> 1 > Example: > {code} > select intKey,intNum from smallA where intNum<>1 > {code} > It returns also rows which have NULL in column intNum > I believe that NULL <> 1 is not true in SQL. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3593) Add "DBF" translator to file "driver" to support DBF files as 'csv' files

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3593?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3593: ------------------------------------- There seems to be a Java library for DBF files here https://github.com/iryndin/jdbf makes nice little project > Add "DBF" translator to file "driver" to support DBF files as 'csv' files > -------------------------------------------------------------------------- > > Key: TEIID-3593 > URL: https://issues.jboss.org/browse/TEIID-3593 > Project: Teiid > Issue Type: Feature Request > Reporter: Tom Johnston > Assignee: Steven Hawkins > > DBF files open with MSExcel, LibreOffice etc.. > I tried to follow the quickstart on Excel files and point to a dbf file instead but it failed... > Seems that there is simply a special header to identify the file as DBF and otherwise it opens as any other CSV file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3593) Add "DBF" translator to file "driver" to support DBF files as 'csv' files

by Tom Johnston (JIRA)

Tom Johnston created TEIID-3593: ----------------------------------- Summary: Add "DBF" translator to file "driver" to support DBF files as 'csv' files Key: TEIID-3593 URL: https://issues.jboss.org/browse/TEIID-3593 Project: Teiid Issue Type: Feature Request Reporter: Tom Johnston Assignee: Steven Hawkins DBF files open with MSExcel, LibreOffice etc.. I tried to follow the quickstart on Excel files and point to a dbf file instead but it failed... Seems that there is simply a special header to identify the file as DBF and otherwise it opens as any other CSV file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3592) XMLFOREST returns source rather than view column names

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3592?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3592. ----------------------------------- Fix Version/s: 8.12 8.11.2 Resolution: Done Updated the logic to always preserve the name. This should be considered for 8.7.x as well. > XMLFOREST returns source rather than view column names > ------------------------------------------------------ > > Key: TEIID-3592 > URL: https://issues.jboss.org/browse/TEIID-3592 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.2 > > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3592) XMLFOREST returns source rather than view column names

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3592?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3592: ---------------------------------- Summary: XMLFOREST returns source rather than view column names (was: REST war returns source column names instead of the virtual table column names) Affects Version/s: 8.0 (was: 8.7.1) > XMLFOREST returns source rather than view column names > ------------------------------------------------------ > > Key: TEIID-3592 > URL: https://issues.jboss.org/browse/TEIID-3592 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3592) REST war returns source column names instead of the virtual table column names

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIID-3592?page=com.atlassian.jira.plugin... ] Ted Jones commented on TEIID-3592: ---------------------------------- Per Steve H. - xmlforest is not preserving the symbol names when the view layer is removed. > REST war returns source column names instead of the virtual table column names > ------------------------------------------------------------------------------ > > Key: TEIID-3592 > URL: https://issues.jboss.org/browse/TEIID-3592 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1 > Reporter: Marc Shirley > Assignee: Ted Jones > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2015