December 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5873) Implement ComplexTypes support in OData EntityType

by Chee Kin Lim (Jira)

Chee Kin Lim created TEIID-5873: ----------------------------------- Summary: Implement ComplexTypes support in OData EntityType Key: TEIID-5873 URL: https://issues.redhat.com/browse/TEIID-5873 Project: Teiid Issue Type: Enhancement Components: OData Affects Versions: 13.0.1 Reporter: Chee Kin Lim Assignee: Steven Hawkins Given the following document in MongoDB matrix_variable collection: { "_id" : ObjectId("5b2367c9c9e77c0007ca0111"), "createdOn" : ISODate("2018-06-15T07:16:25.459Z"), "modifiedOn" : ISODate("2018-07-02T02:04:16.661Z"), "variableId" : "183cf101d2334ac09bd0db9aee96081f", "name" : "lfzq_test", "description" : "", "lastModifiedUserEmail" : "admin1(a)abc.com", "headerRow" : { "rowId" : "0b002942a5b4424f98fcc270af0290c3", "values" : [ "name", "value" ], "isEncrypted" : [ false, true ] }, "rows" : [ { "rowId" : "940467f9bb724d1688086baeec05049b", "values" : [ "lfzq123q", "751c634ca5e24102a00800b386955a5c" ] } ], "deleted" : false } The "headerRow" property is exposed as separate entity type in OData schema, but not "rows" property. I found the following entity types with odata/$metadata: <EntityType Name="headerRow">...</EntityType> <EntityType Name="matrix_variable">...</EntityType> Github repo to showcase the issue: https://github.com/limcheekin/teiid-spring-boot-mongodb-odata Related StackOverflow post: https://stackoverflow.com/a/59385181/303211 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

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 commented on TEIIDSB-144: ---------------------------------------- Either way. I was just flipping it to no longer in progress given the break. > 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)

4 years, 4 months

1
0
0 / 0

[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: -------------------------------------- Do you want me to take over this, you good? > 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)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-147) Caching and materialization changes for JDG / OpenShift

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-147?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-147: --------------------------------- Fix Version/s: 1.3.1 (was: 1.3.0) > Caching and materialization changes for JDG / OpenShift > ------------------------------------------------------- > > Key: TEIIDSB-147 > URL: https://issues.redhat.com/browse/TEIIDSB-147 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core, OpenShift > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 1.3.1 > > > Started this as a higher level issue in Teiid Spring Boot rather than core Teiid since the work won't align well to Teiid 13.1, but some things may need addressed there as well. > Things break down roughly into: > * Single-pod support > ** Define the expectations for how we'll be configured to hit a JDG instance - will it be a user exercise to create if it doesn't exist, will we need to create, will the be a crd strategy for creation, and will it be multi-tenet? There is also the issue / assumption of cache sharing based upon vdb name - is that sufficient for now? > ** validate external materialization to JDG likely using a transactional upsert strategy to avoid issues like TEIID-5436 > * Multi-pod support > ** everything from single-pod support > ** Result set caching needs to directly write batches / results to JDG rather than relying upon on demand replication. > ** requires replacing the logic that detect failed materialization loads > ** internal materialization replacement needs to based upon something more like external materialization, but that can be seen as a next step that is turnkey internal materialization to JDG (little to no user setup required) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-147) Caching and materialization changes for JDG / OpenShift

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-147?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-147: --------------------------------- Sprint: (was: DV Sprint 56) > Caching and materialization changes for JDG / OpenShift > ------------------------------------------------------- > > Key: TEIIDSB-147 > URL: https://issues.redhat.com/browse/TEIIDSB-147 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core, OpenShift > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 1.3.1 > > > Started this as a higher level issue in Teiid Spring Boot rather than core Teiid since the work won't align well to Teiid 13.1, but some things may need addressed there as well. > Things break down roughly into: > * Single-pod support > ** Define the expectations for how we'll be configured to hit a JDG instance - will it be a user exercise to create if it doesn't exist, will we need to create, will the be a crd strategy for creation, and will it be multi-tenet? There is also the issue / assumption of cache sharing based upon vdb name - is that sufficient for now? > ** validate external materialization to JDG likely using a transactional upsert strategy to avoid issues like TEIID-5436 > * Multi-pod support > ** everything from single-pod support > ** Result set caching needs to directly write batches / results to JDG rather than relying upon on demand replication. > ** requires replacing the logic that detect failed materialization loads > ** internal materialization replacement needs to based upon something more like external materialization, but that can be seen as a next step that is turnkey internal materialization to JDG (little to no user setup required) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-149) Support Amazon S3 Transaltor

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-149?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIIDSB-149. ---------------------------------- Resolution: Done Amazon S3 translator is added, however it needs an updated Teiid 13.x version >= 13.0.2 > Support Amazon S3 Transaltor > ---------------------------- > > Key: TEIIDSB-149 > URL: https://issues.redhat.com/browse/TEIIDSB-149 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: datasource > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 1.3.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Provide support for Amazon S3 transaltor in Teiid Spring Boot with an example. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-123) Provide support for Amazon Athena

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-123?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-123: --------------------------------- Fix Version/s: 1.3.1 (was: 1.3.0) > Provide support for Amazon Athena > --------------------------------- > > Key: TEIIDSB-123 > URL: https://issues.redhat.com/browse/TEIIDSB-123 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Priority: Critical > Fix For: 1.3.1 > > > Provide the translator support for Amazon Athena -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-123) Provide support for Amazon Athena

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-123?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-123: --------------------------------- Sprint: (was: DV Sprint 56) > Provide support for Amazon Athena > --------------------------------- > > Key: TEIIDSB-123 > URL: https://issues.redhat.com/browse/TEIIDSB-123 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Priority: Critical > Fix For: 1.3.1 > > > Provide the translator support for Amazon Athena -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

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 commented on TEIIDSB-144: ---------------------------------------- Sounds like the plan is to move back to tomcat-jdbc then and make the appropriate changes at least in teiid-syndesis. > 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

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 stopped 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 > > 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2019