May 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4520) Support for Exasol Connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4520?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4520: --------------------------------------- As long as the string conversion is still compatible with the default format (that is we can convert from that string to the teiid/jdbc type), it's a low priority to match things like the number of fractional second or double trailing zeros. > Support for Exasol Connector > ---------------------------- > > Key: TEIID-4520 > URL: https://issues.jboss.org/browse/TEIID-4520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Andrej Šmigala > Fix For: 10.x, Open To Community > > > Requesting support for Exasol Connector -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4520) Support for Exasol Connector

by Rafal Korytkowski (JIRA)

[ https://issues.jboss.org/browse/TEIID-4520?page=com.atlassian.jira.plugin... ] Rafal Korytkowski edited comment on TEIID-4520 at 5/9/18 9:05 AM: ------------------------------------------------------------------ Thanks for the tip about null ConcatFunctionModifier. Quick progress report. Failures down from 366 to 323. Any hints for changing conversion from timestamp to string to be 2000-01-01 00:00:00.000000 instead of 2000-01-01 00:00:00.0? Nevermind, I guess I need something along these lines: {code:java} convertModifier.addConvert(FunctionModifier.TIMESTAMP, FunctionModifier.STRING, new ConvertModifier.FormatModifier("to_char", TIMESTAMP_FORMAT)); {code} was (Author: rkorytkowski): Thanks for the tip about null ConcatFunctionModifier. Quick progress report. Failures down from 366 to 323. Any hints for changing conversion from timestamp to string to be 2000-01-01 00:00:00.000000 instead of 2000-01-01 00:00:00.0? > Support for Exasol Connector > ---------------------------- > > Key: TEIID-4520 > URL: https://issues.jboss.org/browse/TEIID-4520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Andrej Šmigala > Fix For: 10.x, Open To Community > > > Requesting support for Exasol Connector -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4520) Support for Exasol Connector

by Rafal Korytkowski (JIRA)

[ https://issues.jboss.org/browse/TEIID-4520?page=com.atlassian.jira.plugin... ] Rafal Korytkowski commented on TEIID-4520: ------------------------------------------ Thanks for the tip about null ConcatFunctionModifier. Quick progress report. Failures down from 366 to 323. Any hints for changing conversion from timestamp to string to be 2000-01-01 00:00:00.000000 instead of 2000-01-01 00:00:00.0? > Support for Exasol Connector > ---------------------------- > > Key: TEIID-4520 > URL: https://issues.jboss.org/browse/TEIID-4520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Andrej Šmigala > Fix For: 10.x, Open To Community > > > Requesting support for Exasol Connector -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5337) Naming consistency issues with ddl vdbs

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5337: ------------------------------------- Summary: Naming consistency issues with ddl vdbs Key: TEIID-5337 URL: https://issues.jboss.org/browse/TEIID-5337 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.3 Create is required to use a single part name as the parser and previous logic always assumed it took affect in the current schema. Alter is now allowed to generally resolve, but drop is not. Drop should probably be allowed to act against any schema. We should also consider having the current schema take resolving precedence with alter/drop. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4784) Provide functionality to perform RENAME table in DDL scripts

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4784?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4784. ----------------------------------- Resolution: Done Labels: (was: Beta3) The fix here was quite broad due to intervening changes in the metadata system. We cannot access the full metadata when initially building the vdb, so all of the logic embedded in the parser that did this (mostly in alters) needed pulled out to the DatabaseStore. >From there I've also made the alters consistent in not needed to only act on the current schema - that is you can use qualified names - although we will still allow you to resolve unqualifed even with the schema set, which can be confusing so I'll log an issue for that and potentially giving preference to resolving against the current schema. I believe the only thing that we require to be in the context of the current schema are creates - so a follow on issue will be to allow drops to work as qualified as well. > Provide functionality to perform RENAME table in DDL scripts > ------------------------------------------------------------ > > Key: TEIID-4784 > URL: https://issues.jboss.org/browse/TEIID-4784 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 9.3 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Fix For: 10.3, 10.1.4, 10.2.2 > > > Allow rename commands like: > ALTER TABLE "teiidtest" RENAME TO "tmptbl_teiidtest"; > This should rename the table name teiidtest in the current schema to tmptbl_teiidtest. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4520) Support for Exasol Connector

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4520?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4520: ------------------------------------- There is explicit NULL CONCAT null behavior, I believe we need to match to that. Like in Teiid we support two different types of CONCAT one does NULL and other does the value. We need to match Teiid function to the EXASOL function. The aim of system functions are, Teiid supports a variety of them, we need to figure out which ones are already supported by the source and if they do then try to match them so that they are pushed down to the source. If they need to be supplied more/different parameters you can use "function modifiers" to convert them to a required form before sending for execution. For example, some databases support LCASE whereas others support LOWERCASE, Teiid supports LCASE, so in the translator, you do name change of the function from LCASE to LOWERCASE. We have seen small subtle differences are always there but we need to minimize that, if the behavior is different you can choose to not support that function. If there are some functions that are not supported by Teiid that source supports, then add them as "pushDown" functions, that is the reason there are two types there. > Support for Exasol Connector > ---------------------------- > > Key: TEIID-4520 > URL: https://issues.jboss.org/browse/TEIID-4520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Andrej Šmigala > Fix For: 10.x, Open To Community > > > Requesting support for Exasol Connector -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4784) Provide functionality to perform RENAME table in DDL scripts

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4784?page=com.atlassian.jira.plugin... ] Work on TEIID-4784 started by Steven Hawkins. --------------------------------------------- > Provide functionality to perform RENAME table in DDL scripts > ------------------------------------------------------------ > > Key: TEIID-4784 > URL: https://issues.jboss.org/browse/TEIID-4784 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 9.3 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Labels: Beta3 > Fix For: 10.3, 10.1.4, 10.2.2 > > > Allow rename commands like: > ALTER TABLE "teiidtest" RENAME TO "tmptbl_teiidtest"; > This should rename the table name teiidtest in the current schema to tmptbl_teiidtest. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4520) Support for Exasol Connector

by Rafal Korytkowski (JIRA)

[ https://issues.jboss.org/browse/TEIID-4520?page=com.atlassian.jira.plugin... ] Rafal Korytkowski edited comment on TEIID-4520 at 5/8/18 9:42 AM: ------------------------------------------------------------------ Thanks [~rareddy]! My other question is how do we handle differences between jdbc data sources? E.g. select concat('10', NULL) returns NULL in MySQL, whereas 10 in Exasol. Does developing a translator mean we need to eliminate such differences to have same results or just make sure that queries coming out of TEIID are valid for that particular data source? was (Author: rkorytkowski): Thanks [~rareddy]! My other question is how do we handle differences between jdbc data sources? E.g. select concat("10", NULL) returns NULL in MySQL, whereas 10 in Exasol. Does developing a translator mean we need to eliminate such differences to have same results or just make sure that queries coming out of TEIID are valid for that particular data source? > Support for Exasol Connector > ---------------------------- > > Key: TEIID-4520 > URL: https://issues.jboss.org/browse/TEIID-4520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Andrej Šmigala > Fix For: 10.x, Open To Community > > > Requesting support for Exasol Connector -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4520) Support for Exasol Connector

by Rafal Korytkowski (JIRA)

[ https://issues.jboss.org/browse/TEIID-4520?page=com.atlassian.jira.plugin... ] Rafal Korytkowski edited comment on TEIID-4520 at 5/8/18 9:41 AM: ------------------------------------------------------------------ Thanks [~rareddy]! My other question is how do we handle differences between jdbc data sources? E.g. select concat("10", NULL) returns NULL in MySQL, whereas 10 in Exasol. Does developing a translator mean we need to eliminate such differences to have same results or just make sure that queries coming out of TEIID are valid for that particular data source? was (Author: rkorytkowski): Thanks [~rareddy]! My other question is how do we handle differences between jdbc data sources? E.g. SELECT ASIN(1/ -24); returns -0.0416787324225779 in MySQL, but 0.0 in Exasol. It's because 1 is automatically converted to double in MySQ, whereas in Exasol it needs to be explicit with ASIN(1.0/ -24); (this is actually not the case, just an example). Does developing a translator mean we need to eliminate such differences to have same results or just make sure that queries coming out of TEIID are valid for that particular data source? > Support for Exasol Connector > ---------------------------- > > Key: TEIID-4520 > URL: https://issues.jboss.org/browse/TEIID-4520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Andrej Šmigala > Fix For: 10.x, Open To Community > > > Requesting support for Exasol Connector -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4520) Support for Exasol Connector

by Rafal Korytkowski (JIRA)

[ https://issues.jboss.org/browse/TEIID-4520?page=com.atlassian.jira.plugin... ] Rafal Korytkowski edited comment on TEIID-4520 at 5/8/18 7:52 AM: ------------------------------------------------------------------ Thanks [~rareddy]! My other question is how do we handle differences between jdbc data sources? E.g. SELECT ASIN(1/ -24); returns -0.0416787324225779 in MySQL, but 0.0 in Exasol. It's because 1 is automatically converted to double in MySQ, whereas in Exasol it needs to be explicit with ASIN(1.0/ -24); (this is actually not the case, just an example). Does developing a translator mean we need to eliminate such differences to have same results or just make sure that queries coming out of TEIID are valid for that particular data source? was (Author: rkorytkowski): Thanks [~rareddy]! My other question is how do we handle differences between jdbc data sources? E.g. SELECT ASIN(1/ -24); returns -0.0416787324225779 in MySQL, but 0.0 in Exasol. It's because 1 is automatically converted to double in MySQ, whereas in Exasol it needs to be explicit with ASIN(1.0/ -24); Does developing a translator mean we need to eliminate such differences to have same results or just make sure that queries coming out of TEIID are valid for that particular data source? > Support for Exasol Connector > ---------------------------- > > Key: TEIID-4520 > URL: https://issues.jboss.org/browse/TEIID-4520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Andrej Šmigala > Fix For: 10.x, Open To Community > > > Requesting support for Exasol Connector -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2018