[JBoss JIRA] (TEIID-3946) Version negotiation in JDBC connection
by Marcelo Guimarães (JIRA)
[ https://issues.jboss.org/browse/TEIID-3946?page=com.atlassian.jira.plugin... ]
Marcelo Guimarães commented on TEIID-3946:
------------------------------------------
The problem occurs with ETL Tools. If the driver is outdated, the tool receives a "TEIID40042 Invalid Session ... Session may have already been terminated" error and retries to connect indefinitely, causing troubles for the other clients. When they upgrade de jdbc driver, the error stops.
> Version negotiation in JDBC connection
> --------------------------------------
>
> Key: TEIID-3946
> URL: https://issues.jboss.org/browse/TEIID-3946
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Driver
> Affects Versions: 8.7.4
> Environment: - JDV 6.2
> Reporter: Hisanobu Okuda
> Assignee: Steven Hawkins
> Fix For: 9.0
>
>
> Our customer is providing a service on top of JDV and some of the external clients are still using outdated teiid drivers and wants something they can make for JDV to block a connection if the JDBC Driver used in a client is outdated. This scenario occurs everytime the customer updates JDV. Since there are so much external clients, some of them don't update their JDBC Drivers and this leads to some errors in JDV.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-3937) Multiplying two columns in CASE statement overrides pushdown (Impala)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3937?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3937.
-----------------------------------
Fix Version/s: 9.0
Resolution: Done
This is now addressed in 9.0
> It's not very straightforward, for what that may be worth, even using the overridden settings.xml
Can you describe in more detail what you are seeing (ideally in a forum post) so that we can get that captured / addressed?
> Multiplying two columns in CASE statement overrides pushdown (Impala)
> ---------------------------------------------------------------------
>
> Key: TEIID-3937
> URL: https://issues.jboss.org/browse/TEIID-3937
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.4
> Environment: Ubuntu Trusty
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
> Fix For: 9.0
>
>
> In the Impala translator, pushdown doesn't happen when two columns are multiplied in the THEN portion of a CASE statement with decimal data type.
> //this should push down but does not
> CASE WHEN column1 IS NOT NULL
> THEN column1 * column2
> ELSE column3 END
> //but you can multiply the columns by a constant and it will push down
> CASE WHEN column1 IS NOT NULL
> THEN column1 * 34567
> ELSE column3 END
> //or
> CASE WHEN column1 IS NOT NULL
> THEN 34567 * column2
> ELSE column3 END
> //or casting to consistent datatypes with DECIMAL output
> CASE WHEN column1 IS NOT NULL
> THEN cast(column1 as DECIMAL ) * cast(column2 as DECIMAL )
> ELSE cast(column3 as DECIMAL ) END
> //BUT output it as double with the cast statement above changed and it does push down (so floating point works)
> CASE WHEN column1 IS NOT NULL
> THEN cast(column1 as double ) * cast(column2 as double)
> ELSE cast(column3 as double) END
> Source data types:
> Column1 is DECIMAL
> Column2 is BIGINT/LONG
> Column3 is DECIMAL
> Output column is DECIMAL
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-3937) Multiplying two columns in CASE statement overrides pushdown (Impala)
by Don Krapohl (JIRA)
[ https://issues.jboss.org/browse/TEIID-3937?page=com.atlassian.jira.plugin... ]
Don Krapohl commented on TEIID-3937:
------------------------------------
Thanks! I was just getting my project set up. It's not very straightforward, for what that may be worth, even using the overridden settings.xml. Will push through so I can contribute. Thanks again!
> Multiplying two columns in CASE statement overrides pushdown (Impala)
> ---------------------------------------------------------------------
>
> Key: TEIID-3937
> URL: https://issues.jboss.org/browse/TEIID-3937
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.4
> Environment: Ubuntu Trusty
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
>
> In the Impala translator, pushdown doesn't happen when two columns are multiplied in the THEN portion of a CASE statement with decimal data type.
> //this should push down but does not
> CASE WHEN column1 IS NOT NULL
> THEN column1 * column2
> ELSE column3 END
> //but you can multiply the columns by a constant and it will push down
> CASE WHEN column1 IS NOT NULL
> THEN column1 * 34567
> ELSE column3 END
> //or
> CASE WHEN column1 IS NOT NULL
> THEN 34567 * column2
> ELSE column3 END
> //or casting to consistent datatypes with DECIMAL output
> CASE WHEN column1 IS NOT NULL
> THEN cast(column1 as DECIMAL ) * cast(column2 as DECIMAL )
> ELSE cast(column3 as DECIMAL ) END
> //BUT output it as double with the cast statement above changed and it does push down (so floating point works)
> CASE WHEN column1 IS NOT NULL
> THEN cast(column1 as double ) * cast(column2 as double)
> ELSE cast(column3 as double) END
> Source data types:
> Column1 is DECIMAL
> Column2 is BIGINT/LONG
> Column3 is DECIMAL
> Output column is DECIMAL
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-3937) Multiplying two columns in CASE statement overrides pushdown (Impala)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3937?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3937:
---------------------------------------
After reproducing this locally, I see what is happening. The translator is not marked as requiring a connection for the capabilities, so it is not looking automatically at the version. You can workaround this by manually setting the databaseVersion property on the translator. I'll fix the code for this as well.
> Multiplying two columns in CASE statement overrides pushdown (Impala)
> ---------------------------------------------------------------------
>
> Key: TEIID-3937
> URL: https://issues.jboss.org/browse/TEIID-3937
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.4
> Environment: Ubuntu Trusty
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
>
> In the Impala translator, pushdown doesn't happen when two columns are multiplied in the THEN portion of a CASE statement with decimal data type.
> //this should push down but does not
> CASE WHEN column1 IS NOT NULL
> THEN column1 * column2
> ELSE column3 END
> //but you can multiply the columns by a constant and it will push down
> CASE WHEN column1 IS NOT NULL
> THEN column1 * 34567
> ELSE column3 END
> //or
> CASE WHEN column1 IS NOT NULL
> THEN 34567 * column2
> ELSE column3 END
> //or casting to consistent datatypes with DECIMAL output
> CASE WHEN column1 IS NOT NULL
> THEN cast(column1 as DECIMAL ) * cast(column2 as DECIMAL )
> ELSE cast(column3 as DECIMAL ) END
> //BUT output it as double with the cast statement above changed and it does push down (so floating point works)
> CASE WHEN column1 IS NOT NULL
> THEN cast(column1 as double ) * cast(column2 as double)
> ELSE cast(column3 as double) END
> Source data types:
> Column1 is DECIMAL
> Column2 is BIGINT/LONG
> Column3 is DECIMAL
> Output column is DECIMAL
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-3946) Version negotiation in JDBC connection
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3946?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3946:
----------------------------------
Fix Version/s: 9.0
> This scenario occurs everytime the customer updates JDV
Can this be elaborated on? It is not expected that there would be issues with older clients "everytime" - especially within the same DV major release.
> Version negotiation in JDBC connection
> --------------------------------------
>
> Key: TEIID-3946
> URL: https://issues.jboss.org/browse/TEIID-3946
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Driver
> Affects Versions: 8.7.4
> Environment: - JDV 6.2
> Reporter: Hisanobu Okuda
> Assignee: Steven Hawkins
> Fix For: 9.0
>
>
> Our customer is providing a service on top of JDV and some of the external clients are still using outdated teiid drivers and wants something they can make for JDV to block a connection if the JDBC Driver used in a client is outdated. This scenario occurs everytime the customer updates JDV. Since there are so much external clients, some of them don't update their JDBC Drivers and this leads to some errors in JDV.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-3894) Teiid transport ssl attributes should add some default values
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3894?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3894.
-----------------------------------
Fix Version/s: (was: 8.12.5)
Resolution: Done
Added allowed values and validation of ssl on transport start. This should be considered for 8.12.x as well.
> Teiid transport ssl attributes should add some default values
> -------------------------------------------------------------
>
> Key: TEIID-3894
> URL: https://issues.jboss.org/browse/TEIID-3894
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Fix For: 9.0
>
>
> Execute the following cli
> {code}
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
> /subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
> {code}
> no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
> h3. ssl-mode allowed value
> * enabled
> * login
> * enabled
> h3. ssl-authentication-mode allowed value
> * 1-way
> * 2-way
> * anonymous
> h3. ssl-ssl-protocol default value
> * TLSv1
> h3. ssl-keymanagement-algorithm default value
> * SunX509
> h3. ssl-enabled-cipher-suites default value
> * SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA
> h3. keystore-type default value
> * JKS
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIID-3946) Version negotiation in JDBC connection
by Hisanobu Okuda (JIRA)
Hisanobu Okuda created TEIID-3946:
-------------------------------------
Summary: Version negotiation in JDBC connection
Key: TEIID-3946
URL: https://issues.jboss.org/browse/TEIID-3946
Project: Teiid
Issue Type: Feature Request
Components: JDBC Driver
Affects Versions: 8.7.4
Environment: - JDV 6.2
Reporter: Hisanobu Okuda
Assignee: Steven Hawkins
Our customer is providing a service on top of JDV and some of the external clients are still using outdated teiid drivers and wants something they can make for JDV to block a connection if the JDBC Driver used in a client is outdated. This scenario occurs everytime the customer updates JDV. Since there are so much external clients, some of them don't update their JDBC Drivers and this leads to some errors in JDV.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months