December 2019 - teiid-issues - Jboss List Archives

[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)

6 years

1
0
0 / 0

[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... ] Work on TEIIDSB-144 started by Steven Hawkins. ---------------------------------------------- > 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 > > > 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)

6 years

1
0
0 / 0

[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: ----------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > 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)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5870) Missing newlines in grammar example

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5870?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5870. ----------------------------------- Resolution: Done Corrected the missing new lines. > Missing newlines in grammar example > ----------------------------------- > > Key: TEIID-5870 > URL: https://issues.redhat.com/browse/TEIID-5870 > Project: Teiid > Issue Type: Quality Risk > Components: Documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5870) Missing newlines in grammar example

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5870: ------------------------------------- Summary: Missing newlines in grammar example Key: TEIID-5870 URL: https://issues.redhat.com/browse/TEIID-5870 Project: Teiid Issue Type: Quality Risk Components: Documentation Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 13.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5867) Support capturing the IMPORT FORIGN DATA in DDLStringVisitor

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5867?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5867: --------------------------------------- Upon further review it's not a good fit to make all ddl statements records. Marking as rejected for now until we work out a new strategy under TEIIDTOOLS-781 > Support capturing the IMPORT FORIGN DATA in DDLStringVisitor > ------------------------------------------------------------ > > Key: TEIID-5867 > URL: https://issues.redhat.com/browse/TEIID-5867 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 13.0 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > In DatabaseStore logic the IMPORT FOREIGN DATA WRAPPER is treated as runtime statements that engine is processing at runtime vs build time representation of the VDB. It is a perfectly valid scenario. > However, when working with VDB building, VDB-Import scenarios we need to capture these as is. can we provide a model in DatabaseStore to capture these in certain situations? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5867) Support capturing the IMPORT FORIGN DATA in DDLStringVisitor

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5867?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5867. ----------------------------------- Fix Version/s: (was: 13.1) (was: 13.0.2) Resolution: Rejected > Support capturing the IMPORT FORIGN DATA in DDLStringVisitor > ------------------------------------------------------------ > > Key: TEIID-5867 > URL: https://issues.redhat.com/browse/TEIID-5867 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 13.0 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > In DatabaseStore logic the IMPORT FOREIGN DATA WRAPPER is treated as runtime statements that engine is processing at runtime vs build time representation of the VDB. It is a perfectly valid scenario. > However, when working with VDB building, VDB-Import scenarios we need to capture these as is. can we provide a model in DatabaseStore to capture these in certain situations? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5867) Support capturing the IMPORT FORIGN DATA in DDLStringVisitor

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5867?page=com.atlassian.jira.plugi... ] Work on TEIID-5867 stopped by Steven Hawkins. --------------------------------------------- > Support capturing the IMPORT FORIGN DATA in DDLStringVisitor > ------------------------------------------------------------ > > Key: TEIID-5867 > URL: https://issues.redhat.com/browse/TEIID-5867 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 13.0 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1, 13.0.2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > In DatabaseStore logic the IMPORT FOREIGN DATA WRAPPER is treated as runtime statements that engine is processing at runtime vs build time representation of the VDB. It is a perfectly valid scenario. > However, when working with VDB building, VDB-Import scenarios we need to capture these as is. can we provide a model in DatabaseStore to capture these in certain situations? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-152) Alter / drop will not work with vdb plugin

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-152: -------------------------------------- Summary: Alter / drop will not work with vdb plugin Key: TEIIDSB-152 URL: https://issues.redhat.com/browse/TEIIDSB-152 Project: Teiid Spring Boot Issue Type: Quality Risk Components: core Reporter: Steven Hawkins If you use an alter / drop in the vdb.ddl the result will be an illegalstateexception: {code} Caused by: java.lang.IllegalStateException: TransformationMetadata not yet available at org.teiid.maven.VdbMojoTest.test(VdbMojoTest.java:53) {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIID-5867) Support capturing the IMPORT FORIGN DATA in DDLStringVisitor

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5867?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5867: --------------------------------------- [~rareddy] Actually this requires all statements to be captured in a different way - every alter, drop, etc. to preserve the order. > Support capturing the IMPORT FORIGN DATA in DDLStringVisitor > ------------------------------------------------------------ > > Key: TEIID-5867 > URL: https://issues.redhat.com/browse/TEIID-5867 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 13.0 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1, 13.0.2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > In DatabaseStore logic the IMPORT FOREIGN DATA WRAPPER is treated as runtime statements that engine is processing at runtime vs build time representation of the VDB. It is a perfectly valid scenario. > However, when working with VDB building, VDB-Import scenarios we need to capture these as is. can we provide a model in DatabaseStore to capture these in certain situations? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2019