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 commented on TEIIDSB-155: ---------------------------------------- > Second caches default to non-transactional, so the operator based cache or a cache created on the fly will by non-transactional. For things to work both the remote and local sides need to be setup for transactional support. Actually in the DataGrid configuration it appears that the cache will be created on demand with the client configuration. I'll make sure that works, but will need to get the transactionManager issue resolved as well. > 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 > 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-154) Create an example of materialization with JDG on openshift

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-154?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-154: ---------------------------------------- I've tried in vain to see if we could use a transactional cache - we are blocked by TEIIDSB-155 > Create an example of materialization with JDG on openshift > ---------------------------------------------------------- > > Key: TEIIDSB-154 > URL: https://issues.redhat.com/browse/TEIIDSB-154 > Project: Teiid Spring Boot > Issue Type: Sub-task > Components: documentation, examples > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.1 > > Original Estimate: 1 day, 7 hours > Remaining Estimate: 1 day, 7 hours > > Create an example showing materialization with JDG on openshift. -- 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 edited comment on TEIIDSB-155 at 1/7/20 12:33 PM: ----------------------------------------------------------------- Transactional support should allow us to use the loadnumber / upsert, rather than cache swapping. However there are a couple of issues. First is that this logic does not exist in Teiid, so it's untested from our side. Second caches default to non-transactional, so the operator based cache or a cache created on the fly will by non-transactional. For things to work both the remote and local sides need to be setup for transactional support. Lastly providing the transaction manager to the InfinispanConnectionFactory will require reworking the startup sequence wrt the transactionmanager. Since there's no option for infinispan to use the platform transaction manager, it must use either our adapter or the user supplied transaction manager. The latter is easy to autowire, but the adapter is created later than the datasources are and is not exposed as a bean. was (Author: shawkins): Creating an issue for transactional support - which should allow us to use the loadnumber / upsert, rather than cache swapping. > 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 > 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: ---------------------------------------- Creating an issue for transactional support - which should allow us to use the loadnumber / upsert, rather than cache swapping. > 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 > 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)

Steven Hawkins created TEIIDSB-155: -------------------------------------- Summary: 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 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-154) Create an example of materialization with JDG on openshift

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-154?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-154: ---------------------------------------- I may have been doing a few things wrong or mixing a couple of versions, but I could not get the infinispan operator to start easily on minishift. Rather the approach, which is one of the options from their docs, is to just use okd cluster up. With a 3.11 version, both of the operators come up: {code} git clone https://github.com/infinispan/infinispan-operator cd infinispan-operator #I had to change the permissions locally export KUBECONFIG=/var/lib/origin/openshift.local.config/master/admin.kubeconfig #cluster up a 3.11 version, todo: minishift oc cluster up make run oc apply -f deploy/cr/minimal/cr_minimal.yaml #there is now an infinispan cluster running oc adm policy --as system:admin add-cluster-role-to-user cluster-admin admin #install the teiid operator oc login -u admin ...teiid operator install #note the KUBECONFIG file allows for the infinispan operator install to be done as system:admin on behalf of the user, while our install requires giving the extra role to admin {code} > Create an example of materialization with JDG on openshift > ---------------------------------------------------------- > > Key: TEIIDSB-154 > URL: https://issues.redhat.com/browse/TEIIDSB-154 > Project: Teiid Spring Boot > Issue Type: Sub-task > Components: documentation, examples > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.1 > > Original Estimate: 1 day, 7 hours > Remaining Estimate: 1 day, 7 hours > > Create an example showing materialization with JDG on openshift. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-154) Create an example of materialization with JDG on openshift

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-154?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIIDSB-154: ----------------------------------- Original Estimate: 1 day, 7 hours Remaining Estimate: 1 day, 7 hours > Create an example of materialization with JDG on openshift > ---------------------------------------------------------- > > Key: TEIIDSB-154 > URL: https://issues.redhat.com/browse/TEIIDSB-154 > Project: Teiid Spring Boot > Issue Type: Sub-task > Components: documentation, examples > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.1 > > Original Estimate: 1 day, 7 hours > Remaining Estimate: 1 day, 7 hours > > Create an example showing materialization with JDG on openshift. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-154) Create an example of materialization with JDG on openshift

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-154?page=com.atlassian.jira.plug... ] Work on TEIIDSB-154 started by Steven Hawkins. ---------------------------------------------- > Create an example of materialization with JDG on openshift > ---------------------------------------------------------- > > Key: TEIIDSB-154 > URL: https://issues.redhat.com/browse/TEIIDSB-154 > Project: Teiid Spring Boot > Issue Type: Sub-task > Components: documentation, examples > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.3.1 > > > Create an example showing materialization with JDG on openshift. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

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

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-147?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-147: ---------------------------------------- Created a subtask for an example - that is all we are looking to tackle in the near term (1.3.x). Any issues with commented on here, or captured as other subtasks. > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-154) Create an example of materialization with JDG on openshift

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-154: -------------------------------------- Summary: Create an example of materialization with JDG on openshift Key: TEIIDSB-154 URL: https://issues.redhat.com/browse/TEIIDSB-154 Project: Teiid Spring Boot Issue Type: Sub-task Components: documentation, examples Reporter: Steven Hawkins Fix For: 1.3.1 Create an example showing materialization with JDG on openshift. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2020