[JBoss JIRA] (TEIIDSB-154) Create an example of materialization with JDG on openshift
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-154?focusedWorklogId=12449825&pa... ]
Steven Hawkins logged work on TEIIDSB-154:
------------------------------------------
Author: Steven Hawkins
Created on: 15/Jan/20 12:51 PM
Start Date: 15/Jan/20 12:51 PM
Worklog Time Spent: 4 hours
Issue Time Tracking
-------------------
Remaining Estimate: 1 day, 3 hours (was: 1 day, 7 hours)
Time Spent: 4 hours
Worklog Id: (was: 12449825)
> 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
> Time Spent: 4 hours
> Remaining Estimate: 1 day, 3 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
[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:
----------------------------------------
The infinispan secret serves a dual purpose - it can configure user accounts for infinispan and when generated it's where you can get the password for the user account. However the design of the secret is as a file reference rather than individual values. That's going to require some additional logic on our side to parse that.
> 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
[JBoss JIRA] (TEIIDSB-155) Infinispan configuration should support a transactional cache
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-155?focusedWorklogId=12449823&pa... ]
Steven Hawkins logged work on TEIIDSB-155:
------------------------------------------
Author: Steven Hawkins
Created on: 15/Jan/20 8:16 AM
Start Date: 15/Jan/20 8:16 AM
Worklog Time Spent: 4 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 4 hours)
Time Spent: 1 day, 4 hours (was: 1 day)
Worklog Id: (was: 12449823)
> 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.4.0, 1.3.1
>
> Original Estimate: 1 day, 4 hours
> Time Spent: 1 day, 4 hours
> Remaining Estimate: 0 minutes
>
> 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
[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 resolved TEIIDSB-155.
------------------------------------
Fix Version/s: 1.4.0
Resolution: Done
The changes are in for the 7.6 branch and master. There doesn't seem to be any spot for the docs on the properties on the spring boot side yet. I'll update the Teiid side with the other issue.
Essentially the changes here are:
* Rework of transaction manager logic so that our adapter is installed as the transaction manager bean to be picked up by other things.
* There is a new TransactionMode property, which comes straight from infinispan. The user would set it to NON_XA (1PC) or NON_DURABLE_XA. FULL_XA is not supported.
* When getting/creating a transactional we'll use the the getOrCreateCache method that takes an xml configuration. The default config specifies the isolation level as repeatable_read (which is common) and locking as pessimistic - the default of optimistic is not supported. Some time later if needed we can externalize that config.
* The sasl mechanism is optional as it has a default on the infinispan side. Similarly we set defaults for the realm and server name.
> 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.4.0, 1.3.1
>
> Original Estimate: 1 day, 4 hours
> Time Spent: 1 day
> Remaining Estimate: 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
[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:
--------------------------------------
Possible workaround as a patch which applies for any feature not implemented cases https://github.com/brettwooldridge/HikariCP/issues/1489#issuecomment-5743...
> 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
[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 commented on TEIIDSB-155:
--------------------------------------
> To clarify someone providing the protobuf file (which needs classpath loading as well), is more developer centric than defining the Teiid ddl directly?
IMO, providing a protobuf file more developer-centric than providing DDL. I would expect VDB user to define the DDL for their materialization, they should not care about the target environment in terms of the definition of it. This approach holds good even for say materializing to PostgreSQL.
> Are you implicitly assuming that either the protobuf file will exist or that it's easier to create?
For typical Infinispan "as a" data source, yes, I am expecting the protobuf to be registered in the cache, this is similar to DV expectations with databases. In DV we only create the protobuf underneath automatically when DDL is present on model, and it is transparent to the user.
For developer-centric view, there are couple options we can follow (neither are implemented)
* We can take a look at entity annotations and generate the correct DDL on VDB thus in-turn can generate the protobuf.
* Ask the user to supply the protobuf file as part of data source definition.
> 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
> Time Spent: 1 day
> Remaining Estimate: 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
[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 protobuf file as an example.
So for things to work with the example, the expectation is that the user is installing the protobuf definition on their own.
> I think protobuf way will also help spring boot developer-centric view too.
To clarify someone providing the protobuf file (which needs classpath loading as well), is more developer centric than defining the Teiid ddl directly? Are you implicitly assuming that either the protobuf file will exist or that it's easier to create?
> For materialization, it looks like there is some more automation needed, somewhere down the toolchain, like in "code generation plugin" to generate the DDL based model and inject the Infinispan data source.
I'm not worried about automation yet. The first cut just needs to work. I'll initially assume that the user is responsible for creating the Teiid ddl or protobuf file (once we have that working for spring boot) to represent the materialization target.
> 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
> Time Spent: 1 day
> Remaining Estimate: 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
[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 edited comment on TEIIDSB-155 at 1/14/20 3:28 PM:
---------------------------------------------------------------
In the example, I was only showing this as a SQL client into Infinispan, connecting to an existing cache. The protobuf file as an example. Simple translator for existing cache.
In order to as dynamic cache configuration, I agree this will not work, we would probably need VDB defined like here http://teiid.github.io/teiid-documents/master/content/reference/Infinispa... , "define metadata in ddl" or protobuf classpath discovery. I think protobuf way will also help spring boot developer-centric view too.
For materialization, it looks like there is some more automation needed, somewhere down the toolchain, like in "code generation plugin" to generate the DDL based model and inject the Infinispan data source.
Or another is like a "materialization-starter", which will do tasks similar to that I mentioned about for "code generation"
was (Author: rareddy):
In the example, I was only showing this as a SQL client into Infinispan, connecting to an existing cache. The protobuf file as an example. Simple translator for existing cache.
In order to as dynamic cache configuration, I agree this will not work, we would probably need VDB defined like here http://teiid.github.io/teiid-documents/master/content/reference/Infinispa... , "define metadata in ddl" or protobuf classpath discovery. I think protobuf way will also help spring boot developer-centric view too.
For materialization, it looks like there is some more automation needed, somewhere down the toolchain, like in "code generation plugin" to generate the DDL based model and inject the Infinispan data source.
> 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
> Time Spent: 1 day
> Remaining Estimate: 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
[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 commented on TEIIDSB-155:
--------------------------------------
In the example, I was only showing this as a SQL client into Infinispan, connecting to an existing cache. The protobuf file as an example. Simple translator for existing cache.
In order to as dynamic cache configuration, I agree this will not work, we would probably need VDB defined like here http://teiid.github.io/teiid-documents/master/content/reference/Infinispa... , "define metadata in ddl" or protobuf classpath discovery. I think protobuf way will also help spring boot developer-centric view too.
For materialization, it looks like there is some more automation needed, somewhere down the toolchain, like in "code generation plugin" to generate the DDL based model and inject the Infinispan data source.
> 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
> Time Spent: 1 day
> Remaining Estimate: 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
[JBoss JIRA] (TEIIDSB-155) Infinispan configuration should support a transactional cache
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-155?focusedWorklogId=12449820&pa... ]
Steven Hawkins logged work on TEIIDSB-155:
------------------------------------------
Author: Steven Hawkins
Created on: 14/Jan/20 1:34 PM
Start Date: 14/Jan/20 1:34 PM
Worklog Time Spent: 1 day
Issue Time Tracking
-------------------
Remaining Estimate: 4 hours (was: 1 day, 4 hours)
Time Spent: 1 day
Worklog Id: (was: 12449820)
> 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
> Time Spent: 1 day
> Remaining Estimate: 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