December 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-144) Calling setTransactionIsolation on pg driver causes the connection to be closed

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-144?focusedWorklogId=12449677&pa... ] Steven Hawkins logged work on TEIIDSB-144: ------------------------------------------ Author: Steven Hawkins Created on: 20/Dec/19 2:11 PM Start Date: 20/Dec/19 2:11 PM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 2 hours (was: 4 hours) Time Spent: 2 hours Worklog Id: (was: 12449677) > Calling setTransactionIsolation on pg driver causes the connection to be closed > ------------------------------------------------------------------------------- > > Key: TEIIDSB-144 > URL: https://issues.redhat.com/browse/TEIIDSB-144 > Project: Teiid Spring Boot > Issue Type: Bug > Components: datasource > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 1.3.1 > > Original Estimate: 4 hours > Time Spent: 2 hours > Remaining Estimate: 2 hours > > An attempt to set the isolation level on pg 42.2.8 resulted in an exception SQLSTATE 0a000 - unsupported - which causes the connection pool to mark the connection as broken: > {code} > 2019-11-25 23:07:50.125 WARN 43993 --- [ProcessorQueue6] com.zaxxer.hikari.pool.ProxyConnection : HikariPool-1 - Connection org.postgresql.jdbc.PgConnection@2ffebc7e marked as broken because of SQLSTATE(0A000), ErrorCode(0) > org.postgresql.util.PSQLException: > at org.postgresql.jdbc.PgConnection.setTransactionIsolation(PgConnection.java:851) ~[postgresql-42.2.8.jar:42.2.8] > at com.zaxxer.hikari.pool.ProxyConnection.setTransactionIsolation(ProxyConnection.java:407) ~[HikariCP-3.2.0.jar:na] > at com.zaxxer.hikari.pool.HikariProxyConnection.setTransactionIsolation(HikariProxyConnection.java) ~[HikariCP-3.2.0.jar:na] > at org.teiid.translator.jdbc.JDBCBaseExecution.<init>(JDBCBaseExecution.java:72) ~[translator-jdbc-12.3.0.jar:12.3.0] > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5872) Excel translator should support reading file from Amazon S3

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIID-5872: ----------------------------------- Summary: Excel translator should support reading file from Amazon S3 Key: TEIID-5872 URL: https://issues.redhat.com/browse/TEIID-5872 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 13.1 Excel translator should support reading data from Amazon S3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5871) Amazon S3 translator generates wrong endpoints

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5871?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIID-5871. --------------------------------- Resolution: Done Removed the explicit cast to avoid the issue, able to call from TSB getObject sucessfully > Amazon S3 translator generates wrong endpoints > ---------------------------------------------- > > Key: TEIID-5871 > URL: https://issues.redhat.com/browse/TEIID-5871 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 13.1, 13.0.2 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Amazon S3 translator currently is not working. I see two issues > 1) The Amazon SDK jar that is being used is very old from 2016, this should be updated to latest either 1.11.695 or 2.0. I am guessing 2.0 will be more work that can be handled in a separate issue. > 2) The default endpoints that are generated are wrong for S3, it looks like this has changed by Amazon. These need to be in the form "<bucket>.s3.amazonaws.com" -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5871) Amazon S3 translator generates wrong endpoints

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5871?page=com.atlassian.jira.plugi... ] Ramesh Reddy reopened TEIID-5871: --------------------------------- Reopening because I see the following error when executing from Teiid Spring Boot {code} Caused by: java.lang.ClassCastException: java.util.LinkedList cannot be cast to java.util.ArrayList at org.teiid.translator.amazon.s3.S3ProcedureExecution.getHeader(S3ProcedureExecution.java:429) ~[translator-amazon-s3-13.1.0-SNAPSHOT.jar:13.1.0-SNAPSHOT] at org.teiid.translator.amazon.s3.S3ProcedureExecution.next(S3ProcedureExecution.java:460) ~[translator-amazon-s3-13.1.0-SNAPSHOT.jar:13.1.0-SNAPSHOT] at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:475) ~[teiid-engine-13.1.0-SNAPSHOT.jar:13.1.0-SNAPSHOT] at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:261) ~[teiid-engine-13.1.0-SNAPSHOT.jar:13.1.0-SNAPSHOT] ... 17 common frames omitted {code} > Amazon S3 translator generates wrong endpoints > ---------------------------------------------- > > Key: TEIID-5871 > URL: https://issues.redhat.com/browse/TEIID-5871 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 13.1, 13.0.2 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Amazon S3 translator currently is not working. I see two issues > 1) The Amazon SDK jar that is being used is very old from 2016, this should be updated to latest either 1.11.695 or 2.0. I am guessing 2.0 will be more work that can be handled in a separate issue. > 2) The default endpoints that are generated are wrong for S3, it looks like this has changed by Amazon. These need to be in the form "<bucket>.s3.amazonaws.com" -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5871) Amazon S3 translator generates wrong endpoints

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5871?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIID-5871. --------------------------------- Resolution: Done It turns out only GetObject calls URL has been changed, which is now corrected. > Amazon S3 translator generates wrong endpoints > ---------------------------------------------- > > Key: TEIID-5871 > URL: https://issues.redhat.com/browse/TEIID-5871 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 13.1, 13.0.2 > > > Amazon S3 translator currently is not working. I see two issues > 1) The Amazon SDK jar that is being used is very old from 2016, this should be updated to latest either 1.11.695 or 2.0. I am guessing 2.0 will be more work that can be handled in a separate issue. > 2) The default endpoints that are generated are wrong for S3, it looks like this has changed by Amazon. These need to be in the form "<bucket>.s3.amazonaws.com" -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5871) Amazon S3 translator generates wrong endpoints

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5871?focusedWorklogId=12449675&pag... ] Ramesh Reddy logged work on TEIID-5871: --------------------------------------- Author: Ramesh Reddy Created on: 20/Dec/19 11:18 AM Start Date: 20/Dec/19 11:18 AM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 2 hours Worklog Id: (was: 12449675) > Amazon S3 translator generates wrong endpoints > ---------------------------------------------- > > Key: TEIID-5871 > URL: https://issues.redhat.com/browse/TEIID-5871 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 13.1, 13.0.2 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Amazon S3 translator currently is not working. I see two issues > 1) The Amazon SDK jar that is being used is very old from 2016, this should be updated to latest either 1.11.695 or 2.0. I am guessing 2.0 will be more work that can be handled in a separate issue. > 2) The default endpoints that are generated are wrong for S3, it looks like this has changed by Amazon. These need to be in the form "<bucket>.s3.amazonaws.com" -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5871) Amazon S3 translator generates wrong endpoints

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5871?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-5871: -------------------------------- Story Points: 0.5 (was: 1) > Amazon S3 translator generates wrong endpoints > ---------------------------------------------- > > Key: TEIID-5871 > URL: https://issues.redhat.com/browse/TEIID-5871 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 13.1, 13.0.2 > > > Amazon S3 translator currently is not working. I see two issues > 1) The Amazon SDK jar that is being used is very old from 2016, this should be updated to latest either 1.11.695 or 2.0. I am guessing 2.0 will be more work that can be handled in a separate issue. > 2) The default endpoints that are generated are wrong for S3, it looks like this has changed by Amazon. These need to be in the form "<bucket>.s3.amazonaws.com" -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-153) RDBMS example failing

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-153?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIIDSB-153. ------------------------------------ Resolution: Done Updated the example property and used the transactional annotation to prevent exceptions related to not using a spring managed transaction. > RDBMS example failing > --------------------- > > Key: TEIIDSB-153 > URL: https://issues.redhat.com/browse/TEIIDSB-153 > Project: Teiid Spring Boot > Issue Type: Bug > Components: examples > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.0 > > > Running the rdbms Application we get: > {code} > Caused by: java.lang.IllegalArgumentException: jdbcUrl is required with driverClassName. > at com.zaxxer.hikari.HikariConfig.validate(HikariConfig.java:951) ~[HikariCP-3.2.0.jar:na] > at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:109) ~[HikariCP-3.2.0.jar:na] > at org.springframework.jdbc.datasource.DataSourceUtils.fetchConnection(DataSourceUtils.java:157) ~[spring-jdbc-5.1.8.RELEASE.jar:5.1.8.RELEASE] > at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:115) ~[spring-jdbc-5.1.8.RELEASE.jar:5.1.8.RELEASE] > at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:78) ~[spring-jdbc-5.1.8.RELEASE.jar:5.1.8.RELEASE] > at org.springframework.jdbc.datasource.init.DatabasePopulatorUtils.execute(DatabasePopulatorUtils.java:46) ~[spring-jdbc-5.1.8.RELEASE.jar:5.1.8.RELEASE] > ... 46 common frames omitted > {code} > Just needs a property change. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5871) Amazon S3 translator generates wrong endpoints

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5871?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIID-5871: ------------------------------------- I was mistaken about #1 above, the translator does not use the aws library at all, just plain http calls, so there is no version degradation. > Amazon S3 translator generates wrong endpoints > ---------------------------------------------- > > Key: TEIID-5871 > URL: https://issues.redhat.com/browse/TEIID-5871 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 13.1, 13.0.2 > > > Amazon S3 translator currently is not working. I see two issues > 1) The Amazon SDK jar that is being used is very old from 2016, this should be updated to latest either 1.11.695 or 2.0. I am guessing 2.0 will be more work that can be handled in a separate issue. > 2) The default endpoints that are generated are wrong for S3, it looks like this has changed by Amazon. These need to be in the form "<bucket>.s3.amazonaws.com" -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5871) Amazon S3 translator generates wrong endpoints

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIID-5871?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-5871: -------------------------------- Story Points: 1 > Amazon S3 translator generates wrong endpoints > ---------------------------------------------- > > Key: TEIID-5871 > URL: https://issues.redhat.com/browse/TEIID-5871 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 13.1, 13.0.2 > > > Amazon S3 translator currently is not working. I see two issues > 1) The Amazon SDK jar that is being used is very old from 2016, this should be updated to latest either 1.11.695 or 2.0. I am guessing 2.0 will be more work that can be handled in a separate issue. > 2) The default endpoints that are generated are wrong for S3, it looks like this has changed by Amazon. These need to be in the form "<bucket>.s3.amazonaws.com" -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2019