[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 updated TEIIDSB-144:
-----------------------------------
Priority: Critical (was: Major)
> 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.0
>
>
> 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
[JBoss JIRA] (TEIID-5866) Teiid embedded does not implement active vdb import management
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5866:
-------------------------------------
Summary: Teiid embedded does not implement active vdb import management
Key: TEIID-5866
URL: https://issues.redhat.com/browse/TEIID-5866
Project: Teiid
Issue Type: Quality Risk
Components: Embedded
Reporter: Steven Hawkins
Assignee: Steven Hawkins
This should initially be resolved by calling out the difference in handling in the docs. In short when you use vdb imports in embedded the import is processed at deployment time only. If the imported vdb later changes, it will cause any changes in importing vdbs.
Note that in teiid-syndesis this import management logic was added via a custom vdb lifecycle listener, but that isn't quite the best solution given that we shouldn't be doing a lot of work in that thread.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5835) Upgrade Apache Olingo to a final version of 4.7
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5835?focusedWorklogId=12448501&pag... ]
Steven Hawkins logged work on TEIID-5835:
-----------------------------------------
Author: Steven Hawkins
Created on: 10/Dec/19 8:12 AM
Start Date: 10/Dec/19 8:12 AM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Time Spent: 1 hour
Worklog Id: (was: 12448501)
> Upgrade Apache Olingo to a final version of 4.7
> -----------------------------------------------
>
> Key: TEIID-5835
> URL: https://issues.redhat.com/browse/TEIID-5835
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 13.x
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 13.0
>
> Original Estimate: 1 hour
> Time Spent: 1 hour
> Remaining Estimate: 0 minutes
>
> Teiid needs to upgrade from the olingo 4.7 SNAPSHOT.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5835) Upgrade Apache Olingo to a final version of 4.7
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5835?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5835.
-----------------------------------
Resolution: Done
Marking as resolved again now that we've worked out the jackson issue - which seems like it will hit again very soon as various components align to newer / different versions.
> Upgrade Apache Olingo to a final version of 4.7
> -----------------------------------------------
>
> Key: TEIID-5835
> URL: https://issues.redhat.com/browse/TEIID-5835
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 13.x
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 13.0
>
> Original Estimate: 1 hour
> Remaining Estimate: 0 minutes
>
> Teiid needs to upgrade from the olingo 4.7 SNAPSHOT.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5850) DDL server and foreign data wrapper handling is unclear
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5850?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-5850:
---------------------------------------
Mostly. create server will take options only for the connection still, so instead of three statements:
CREATE FOREIGN DATA WRAPPER salesforce;
CREATE FOREIGN DATA WRAPPER mysalesforce TYPE salesforce (supportsOrderby true);
CREATE SERVER myServer FOREIGN DATA WRAPPER mysalesforce;
You just have two:
CREATE FOREIGN DATA WRAPPER mysalesforce TYPE salesforce (supportsOrderby true);
CREATE SERVER myServer FOREIGN DATA WRAPPER mysalesforce;
> DDL server and foreign data wrapper handling is unclear
> -------------------------------------------------------
>
> Key: TEIID-5850
> URL: https://issues.redhat.com/browse/TEIID-5850
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0
>
> Original Estimate: 6 hours
> Time Spent: 4 hours
> Remaining Estimate: 2 hours
>
> CREATE server statements in DDL are effectively ignored in the conversion to runtime state - they are simply validated. Similarly a CREATE foreign data wrapper statement that does not specify a type is ignored.
> Attempting to do something like:
> {code}
> CREATE FOREIGN DATA WRAPPER salesforce;
> CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS ("resource-name" 'salesforce', supportsOrderBy true);
> {code}
> or
> {code}
> CREATE FOREIGN DATA WRAPPER salesforce OPTIONS (supportsOrderBy true);
> CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS ("resource-name" 'salesforce');
> {code}
> will not result in supportsOrderBy being set on the translator.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5850) DDL server and foreign data wrapper handling is unclear
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIID-5850?page=com.atlassian.jira.plugi... ]
Ramesh Reddy commented on TEIID-5850:
-------------------------------------
[~shawkins] so in the case of
{code}
CREATE FOREIGN DATA WRAPPER mysalesforce TYPE salesforce (supportsOrderby true)
{code}
can we directly write?
{code}
CREATE SERVER myServer FOREIGN DATA WRAPPER salesforce OPTIONS (supportsOrderby true)
{code}
> DDL server and foreign data wrapper handling is unclear
> -------------------------------------------------------
>
> Key: TEIID-5850
> URL: https://issues.redhat.com/browse/TEIID-5850
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0
>
> Original Estimate: 6 hours
> Time Spent: 4 hours
> Remaining Estimate: 2 hours
>
> CREATE server statements in DDL are effectively ignored in the conversion to runtime state - they are simply validated. Similarly a CREATE foreign data wrapper statement that does not specify a type is ignored.
> Attempting to do something like:
> {code}
> CREATE FOREIGN DATA WRAPPER salesforce;
> CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS ("resource-name" 'salesforce', supportsOrderBy true);
> {code}
> or
> {code}
> CREATE FOREIGN DATA WRAPPER salesforce OPTIONS (supportsOrderBy true);
> CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS ("resource-name" 'salesforce');
> {code}
> will not result in supportsOrderBy being set on the translator.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (TEIID-5862) TEIID-5314 does not account for env key name restrictions
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5862?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5862.
-----------------------------------
Resolution: Done
Changed the logic to handle env properties separately so that we can tell when to check with snake case. Added a doc note about this as well.
> TEIID-5314 does not account for env key name restrictions
> ----------------------------------------------------------
>
> Key: TEIID-5862
> URL: https://issues.redhat.com/browse/TEIID-5862
> Project: Teiid
> Issue Type: Quality Risk
> Components: Common
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 13.0
>
> Original Estimate: 4 hours
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> The logic introduced in TEIID-5314 assumes that env variables can be referenced with existing teiid keys. This was supposed to work with thorntail, but I think that it would have needed to either preprocess the env and populate additional system properties, or otherwise manipulate the env keys. In any event the logic is not sound in general.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years