[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 reassigned TEIID-5871:
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> 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)
4 years, 4 months
[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... ]
Work on TEIID-5871 started by Ramesh Reddy.
-------------------------------------------
> 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)
4 years, 4 months
[JBoss JIRA] (TEIIDSB-144) Calling setTransactionIsolation on pg driver causes the connection to be closed
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-144?page=com.atlassian.jira.plug... ]
Ramesh Reddy commented on TEIIDSB-144:
--------------------------------------
I did start out with tomcat-jdbc, however when we moved to Spring 2.x the default was Hikari, rather than going after explicitly disabling it, I just tried to use it. I guess we should move now, I can't think of any reason to stay with Hikari. If this is fixed in future we can look back.
> 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
> Remaining Estimate: 4 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)
4 years, 4 months
[JBoss JIRA] (TEIID-5871) Amazon S3 translator generates wrong endpoints
by Ramesh Reddy (Jira)
Ramesh Reddy created TEIID-5871:
-----------------------------------
Summary: 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: Steven Hawkins
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)
4 years, 4 months
[JBoss JIRA] (TEIIDSB-153) RDBMS example failing
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-153?page=com.atlassian.jira.plug... ]
Work on TEIIDSB-153 started by Steven Hawkins.
----------------------------------------------
> 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)
4 years, 4 months
[JBoss JIRA] (TEIIDSB-153) RDBMS example failing
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-153:
--------------------------------------
Summary: 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
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)
4 years, 4 months
[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?page=com.atlassian.jira.plug... ]
Steven Hawkins commented on TEIIDSB-144:
----------------------------------------
The problem line: https://github.com/brettwooldridge/HikariCP/blob/109b910fbfc2d95b920fde77...
There is no a pr open to customize the pool behavior - https://github.com/brettwooldridge/HikariCP/pull/1509
No indication of when that will be picked up.
In the meantime our options are:
- use tomcat jdbc as the pooling mechanism. Similar to https://github.com/javamelody/javamelody/issues/801 The problems here are that teiid-syndesis includes pool initialization assuming hikari and that tomcat does no purging at all, so a test/validation method must be turned on.
- create a proxy layer to trap exceptions that could be a problem
- put a bunch of conditionals in teiid about when to is allowed to make calls that may not be implemented
- just wait for the fix...
Other than doing nothing, I'd vote for switching to tomcat jdbc. [~rareddy] do you have a vote?
> 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
> Remaining Estimate: 4 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)
4 years, 4 months
[JBoss JIRA] (TEIID-5869) Update core-release profile
by Van Halbert (Jira)
[ https://issues.redhat.com/browse/TEIID-5869?focusedWorklogId=12449669&pag... ]
Van Halbert logged work on TEIID-5869:
--------------------------------------
Author: Van Halbert
Created on: 19/Dec/19 2:47 PM
Start Date: 19/Dec/19 2:47 PM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Remaining Estimate: 30 minutes (was: 1 hour, 30 minutes)
Time Spent: 1 hour, 30 minutes (was: 30 minutes)
Worklog Id: (was: 12449669)
> Update core-release profile
> ---------------------------
>
> Key: TEIID-5869
> URL: https://issues.redhat.com/browse/TEIID-5869
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 13.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Major
> Fix For: 13.1, 13.0.2
>
> Original Estimate: 2 hours
> Time Spent: 1 hour, 30 minutes
> Remaining Estimate: 30 minutes
>
> For the 7.6 release, need to update the core-release profile so that it builds all connectors except the following:
> - infinispan (removed from 7.6 release)
> - sandbox
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 4 months