[JBoss JIRA] (TEIID-5875) MongoDB metadata import can create tables with no columns
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5875:
-------------------------------------
Summary: MongoDB metadata import can create tables with no columns
Key: TEIID-5875
URL: https://issues.redhat.com/browse/TEIID-5875
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 13.1, 13.0.2
The mongodb metadata import adds tables before determining what columns are available. In some circumstances this results in tables with no columns.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIID-5874) Infinispan connection should support a transactional cache
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5874?page=com.atlassian.jira.plugi... ]
Steven Hawkins moved TEIIDSB-156 to TEIID-5874:
-----------------------------------------------
Project: Teiid (was: Teiid Spring Boot)
Key: TEIID-5874 (was: TEIIDSB-156)
Component/s: Misc. Connectors
(was: datasource)
Fix Version/s: 13.x
(was: 1.3.1)
> Infinispan connection should support a transactional cache
> ----------------------------------------------------------
>
> Key: TEIID-5874
> URL: https://issues.redhat.com/browse/TEIID-5874
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 13.x
>
>
> 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)
6 years, 2 months
[JBoss JIRA] (TEIIDSB-156) Infinispan connection should support a transactional cache
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-156:
--------------------------------------
Summary: Infinispan connection should support a transactional cache
Key: TEIIDSB-156
URL: https://issues.redhat.com/browse/TEIIDSB-156
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)
6 years, 2 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 take-aways:
1. The underlying exception is misleading. It's not an authorization issue, it's that if the cache would be created using the default template it would not support transactions.
2. You have to use an xml configuration (or install a cache template) that specifies a transactional cache. It also must specify locking PESSIMISTIC as the default OPTIMISTIC requires versioning. I do not see any built-in cache templates that are transactional. This means that our connection code is effectively responsible for fully defining the cache - which does not seem ideal. That probably needs externalized in some way.
3. getCache will throw an exception in the transactional case rather than returning a null cache. The connection code needs to be updated accordingly.
> 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)
6 years, 2 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:
----------------------------------------
Running these changes against an infinispan cluster in openshift results in:
{code}
org.infinispan.client.hotrod.exceptions.HotRodClientException: java.lang.SecurityException: ISPN006017: Unauthorized 'PREPARE_TX_2' operation
at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:337) ~[infinispan-client-hotrod-10.0.1.Final.jar:10.0.1.Final]
at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:176) ~[infinispan-client-hotrod-10.0.1.Final.jar:10.0.1.Final]
{code}
During the pre-check before creating the remote transactional cache. This is an infinispan DataGrid created by their operator using either their generated developer or operator accounts.
I'll poke around in the infinispan code before raising an issue on their side.
> 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)
6 years, 2 months
[JBoss JIRA] (TEIIDSB-153) RDBMS example failing
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-153?focusedWorklogId=12449695&pa... ]
Steven Hawkins logged work on TEIIDSB-153:
------------------------------------------
Author: Steven Hawkins
Created on: 09/Jan/20 10:21 AM
Start Date: 09/Jan/20 10:21 AM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 1 hour)
Time Spent: 1 hour
Worklog Id: (was: 12449695)
> RDBMS example failing
> ---------------------
>
> Key: TEIIDSB-153
> URL: https://issues.redhat.com/browse/TEIIDSB-153
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: examples
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.3.0
>
> Original Estimate: 1 hour
> Time Spent: 1 hour
> Remaining Estimate: 0 minutes
>
> Running the rdbms Application we get:
> {code}
> Caused by: java.lang.IllegalArgumentException: jdbcUrl is required with driverClassName.
> at com.zaxxer.hikari.HikariConfig.validate(HikariConfig.java:951) ~[HikariCP-3.2.0.jar:na]
> at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:109) ~[HikariCP-3.2.0.jar:na]
> at org.springframework.jdbc.datasource.DataSourceUtils.fetchConnection(DataSourceUtils.java:157) ~[spring-jdbc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
> at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:115) ~[spring-jdbc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
> at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:78) ~[spring-jdbc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
> at org.springframework.jdbc.datasource.init.DatabasePopulatorUtils.execute(DatabasePopulatorUtils.java:46) ~[spring-jdbc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
> ... 46 common frames omitted
> {code}
> Just needs a property change.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (TEIIDSB-153) RDBMS example failing
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-153?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIIDSB-153:
-----------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
> RDBMS example failing
> ---------------------
>
> Key: TEIIDSB-153
> URL: https://issues.redhat.com/browse/TEIIDSB-153
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: examples
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.3.0
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Running the rdbms Application we get:
> {code}
> Caused by: java.lang.IllegalArgumentException: jdbcUrl is required with driverClassName.
> at com.zaxxer.hikari.HikariConfig.validate(HikariConfig.java:951) ~[HikariCP-3.2.0.jar:na]
> at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:109) ~[HikariCP-3.2.0.jar:na]
> at org.springframework.jdbc.datasource.DataSourceUtils.fetchConnection(DataSourceUtils.java:157) ~[spring-jdbc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
> at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:115) ~[spring-jdbc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
> at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:78) ~[spring-jdbc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
> at org.springframework.jdbc.datasource.init.DatabasePopulatorUtils.execute(DatabasePopulatorUtils.java:46) ~[spring-jdbc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
> ... 46 common frames omitted
> {code}
> Just needs a property change.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 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:
----------------------------------------
Yes, it's cleaned up now.
> 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)
6 years, 2 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:
--------------------------------------
looks like other changes are intermixed in there, but the basic idea is to push the TM to the source level?
> 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)
6 years, 2 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:
----------------------------------------
I believe these are the changes to get this to work: https://github.com/teiid/teiid-spring-boot/compare/master...shawkins:TEII...
I went round and round with spring on how to introduce our platform transaction manager adapter into the mix. [~rareddy] let me know if you have any qualms with this. I'll do some more testing before submitting the pr.
> 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)
6 years, 2 months