January 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-155) Infinispan configuration should support a transactional cache

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-155?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIIDSB-155: ----------------------------------- Original Estimate: 1 day, 4 hours Remaining Estimate: 1 day, 4 hours > Infinispan configuration should support a transactional cache > ------------------------------------------------------------- > > Key: TEIIDSB-155 > URL: https://issues.redhat.com/browse/TEIIDSB-155 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: datasource > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.1 > > Original Estimate: 1 day, 4 hours > Remaining Estimate: 1 day, 4 hours > > The configuration should allow for single phase commit and non-recoverable xa. This will need to change the transaction support on the translator, set the transaction config, and register a transactionManager lookup that can find the configured transaction manager. > The infinispan operator does not provide a way to configure the transaction support of the cache, so this may not fully work yet - I'll test to see what happens both with the default cache and with trying to create one on demand. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-155) Infinispan configuration should support a transactional cache

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-155?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-155: ---------------------------------------- Added a pr. [~rareddy] as far as I can see there are some missing steps or additional changes to the current example. The importer is configured with protobuf name, which expects that protobuf definition to already be in the cache. If not then we are failing at import time. The importer can also take a file path to a protobuf file - but in this example the file will be a classpath resource which doesn't appear like it will work. What was your expectation when you first did the example? > Infinispan configuration should support a transactional cache > ------------------------------------------------------------- > > Key: TEIIDSB-155 > URL: https://issues.redhat.com/browse/TEIIDSB-155 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: datasource > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.1 > > > The configuration should allow for single phase commit and non-recoverable xa. This will need to change the transaction support on the translator, set the transaction config, and register a transactionManager lookup that can find the configured transaction manager. > The infinispan operator does not provide a way to configure the transaction support of the cache, so this may not fully work yet - I'll test to see what happens both with the default cache and with trying to create one on demand. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-155) Infinispan configuration should support a transactional cache

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-155?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-155: ---------------------------------------- The good news is that this seems to work. The bad news is that it requires more extensive changes to security and how we get caches. I'll have a pr today. > Infinispan configuration should support a transactional cache > ------------------------------------------------------------- > > Key: TEIIDSB-155 > URL: https://issues.redhat.com/browse/TEIIDSB-155 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: datasource > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.1 > > > The configuration should allow for single phase commit and non-recoverable xa. This will need to change the transaction support on the translator, set the transaction config, and register a transactionManager lookup that can find the configured transaction manager. > The infinispan operator does not provide a way to configure the transaction support of the cache, so this may not fully work yet - I'll test to see what happens both with the default cache and with trying to create one on demand. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 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: DV Sprint 58 > 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 > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 1.4.0, 1.3.1 > > > Provide the translator support for Amazon Athena -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 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: --------------------------------- Story Points: 1 > 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 > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 1.4.0, 1.3.1 > > > Provide the translator support for Amazon Athena -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-27) Created targeted documentation

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-27?page=com.atlassian.jira.plugi... ] Ramesh Reddy resolved TEIIDSB-27. --------------------------------- Resolution: Done This will be tracked further based on the documentation team's efforts. The community docs are already been separated out > Created targeted documentation > ------------------------------ > > Key: TEIIDSB-27 > URL: https://issues.redhat.com/browse/TEIIDSB-27 > Project: Teiid Spring Boot > Issue Type: Task > Components: documentation > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.1 > > > It's expected that all developer oriented aspects will be self documented with javadoc and examples (udfs, pom options, configuration, custom extensions, etc.). However the Teiid ddl, sql - and in particular the presentation of topics that were presented separately such as data roles - need to be covered by documentation that does not reference topics such as Designer, wildfly/cli, xml vdbs, etc. We should probably also discuss if it makes any sense to still offer the local adminapi. > We expect to receive some input from the documentation group around doc structure and strategies for generating specific documentation sets off of a master. At a high level we have: > Administrator’s Guide - WildFly specific and should mostly be replaced by examples > Caching Guide - References adminapi, Teiid JDBC, xml vdbs.. > Client Developer’s Guide - Teiid JDBC > Developer’s Guide - References WildFly and several arche-types are specific to WildFly/JEE - should mostly be replaced by examples > Embedded Guide - Should mostly be replaced by examples > Reference Guide - References XML vdbs > Security Guide - WildFly specific and should mostly be replaced by examples, but a lot is TDB -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-155) Infinispan configuration should support a transactional cache

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-155?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-155: --------------------------------- Sprint: DV Sprint 57, DV Sprint 58 (was: DV Sprint 57) > Infinispan configuration should support a transactional cache > ------------------------------------------------------------- > > Key: TEIIDSB-155 > URL: https://issues.redhat.com/browse/TEIIDSB-155 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: datasource > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.1 > > > The configuration should allow for single phase commit and non-recoverable xa. This will need to change the transaction support on the translator, set the transaction config, and register a transactionManager lookup that can find the configured transaction manager. > The infinispan operator does not provide a way to configure the transaction support of the cache, so this may not fully work yet - I'll test to see what happens both with the default cache and with trying to create one on demand. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 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: DV Sprint 58 > 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, 11 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 updated TEIIDSB-144: --------------------------------- Sprint: DV Sprint 55, DV Sprint 56, DV Sprint 58 (was: DV Sprint 55, DV Sprint 56) > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-51) Define expectations for runtime metadata

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-51?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-51: ------------------------------------- Documentation task, need to document limitations. It is is SB issue > Define expectations for runtime metadata > ---------------------------------------- > > Key: TEIIDSB-51 > URL: https://issues.redhat.com/browse/TEIIDSB-51 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: documentation > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.3.1 > > > At a high level there are potentially three modes for our ddl: > 1. Interactive - there was some work toward this, but it needed to only be a "developer mode" as it would reload the vdb on each metadata change. There is a lot about the transactionality of DDL updates that our current simplistic metadata model does not support, which makes this hard to fully implement. We haven't talked about this much in relation to Teiid Spring Boot, but ideally there should be a way for developers to test incremental changes without full rebuilds. > 2. Dynamic - the term is a bit dated, but this refers to any vdb that performs import from a metadata repository that has runtime dependencies. By design this allows for a simple vdb definition and options for caching or re-importing on reload. In a container environment metadata caching no longer makes sense unless we use a volume. Depending upon your viewpoint allowing for runtime import of metadata is potentially a point of mutability that is also not needed in a container environment. > 3. Static - much like our old .index designer vdbs there are benefits to having the full metadata already available to the vdb/image. There is a lot of work that we do lazily at runtime that can be moved to an earlier phase - primarily generating the rest and odata layers, but it would also include the pg system table materializations. For Teiid Spring Boot or usage in containers in general what this would look like is a build phase for the vdb such that it could obtain appropriate metadata and initialize as much as possible statically (eventually for quarkus vm snapshotting). The only metadata that would not be fresh potentially would be the costing metadata - however that is problematic as is and will eventually need a progressive optimization strategy employing a persistent store. > As of now we are currently focused just on #2. As we look toward operators, we should start thinking about #3. > #1 would come into play if/when we start looking at local development options using vs code. > We can treat this issue as an epic and a place to centralize discussion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2020