[JBoss JIRA] (TEIIDSB-198) Align with 2.2.6 spring boot
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-198?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIIDSB-198:
-----------------------------------
Summary: Align with 2.2.6 spring boot (was: Align with later 2.2.4 spring boot )
Nevermind, syndesis is updating now: https://github.com/syndesisio/syndesis/commit/4372d4f2b29edb5f03f5c07cfc0...
So this will cover the migration to 2.2.6
> Align with 2.2.6 spring boot
> -----------------------------
>
> Key: TEIIDSB-198
> URL: https://issues.redhat.com/browse/TEIIDSB-198
> Project: Teiid Spring Boot
> Issue Type: Task
> Components: core
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 1.5.0
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Due to the wildfly updates of TEIID-5859 that pull in a newer cxf and related dependencies, we end up with version conflicts. The best fix seems to be bumping Teiid Spring Boot to a later version. The only downside is that later version of spring boot have switched to jakarta javax dependencies, so we get a lot of duplicate / different class warnings. We can ignore the errors/warning, try to exclude incoming dependencies from Teiid, or switch Teiid to use jakarta instead...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (TEIIDSB-198) Align with 2.2.6 spring boot
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-198?page=com.atlassian.jira.plug... ]
Steven Hawkins reassigned TEIIDSB-198:
--------------------------------------
Assignee: Steven Hawkins
> Align with 2.2.6 spring boot
> -----------------------------
>
> Key: TEIIDSB-198
> URL: https://issues.redhat.com/browse/TEIIDSB-198
> Project: Teiid Spring Boot
> Issue Type: Task
> Components: core
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.5.0
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Due to the wildfly updates of TEIID-5859 that pull in a newer cxf and related dependencies, we end up with version conflicts. The best fix seems to be bumping Teiid Spring Boot to a later version. The only downside is that later version of spring boot have switched to jakarta javax dependencies, so we get a lot of duplicate / different class warnings. We can ignore the errors/warning, try to exclude incoming dependencies from Teiid, or switch Teiid to use jakarta instead...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (TEIIDSB-192) Document migration for alias names
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-192?page=com.atlassian.jira.plug... ]
Steven Hawkins commented on TEIIDSB-192:
----------------------------------------
https://github.com/teiid/teiid-spring-boot/pull/223 adds the salesforce 41 and 34 translator names as migration targets as well by adding additional aliases for the salesforce connection factory. At this point I believe we have our bases covered in terms of allowing existing names to simply work without a manual effort or specific migration logic. The things that could be documented:
* just like the warning in teiid, say that if the saleforce url is not specified it is not guaranteed across releases which api version you are hitting. also we can note the difference of having just a single translator supported - I'll handle that in the base Teiid docs with templating.
* update whatever documentation may exist as to the full set of names as the base docs don't mention anything about the driver specific x-db names nor for now athena.
> Document migration for alias names
> ----------------------------------
>
> Key: TEIIDSB-192
> URL: https://issues.redhat.com/browse/TEIIDSB-192
> Project: Teiid Spring Boot
> Issue Type: Task
> Components: documentation
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.5.0
>
> Original Estimate: 4 hours
> Time Spent: 2 hours
> Remaining Estimate: 2 hours
>
> Translators like salesforce and actian-vector has new name in the spring boot, we need to either document or switch back to original names.
> Also if we are updating migration utilities we can build in smarts into it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (TEIIDSB-198) Align with later 2.2.4 spring boot
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-198?page=com.atlassian.jira.plug... ]
Steven Hawkins commented on TEIIDSB-198:
----------------------------------------
> Will 2.2.6 work as this is the next supported version from Runtimes? TEIIDSB-196
For now that will push us ahead of syndesis. I'd just do that update after this one.
> Align with later 2.2.4 spring boot
> -----------------------------------
>
> Key: TEIIDSB-198
> URL: https://issues.redhat.com/browse/TEIIDSB-198
> Project: Teiid Spring Boot
> Issue Type: Task
> Components: core
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 1.5.0
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Due to the wildfly updates of TEIID-5859 that pull in a newer cxf and related dependencies, we end up with version conflicts. The best fix seems to be bumping Teiid Spring Boot to a later version. The only downside is that later version of spring boot have switched to jakarta javax dependencies, so we get a lot of duplicate / different class warnings. We can ignore the errors/warning, try to exclude incoming dependencies from Teiid, or switch Teiid to use jakarta instead...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (TEIIDSB-198) Align with later 2.2.4 spring boot
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-198?page=com.atlassian.jira.plug... ]
Ramesh Reddy commented on TEIIDSB-198:
--------------------------------------
Will 2.2.6 work as this is the next supported version from Runtimes? TEIIDSB-196
> Align with later 2.2.4 spring boot
> -----------------------------------
>
> Key: TEIIDSB-198
> URL: https://issues.redhat.com/browse/TEIIDSB-198
> Project: Teiid Spring Boot
> Issue Type: Task
> Components: core
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 1.5.0
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Due to the wildfly updates of TEIID-5859 that pull in a newer cxf and related dependencies, we end up with version conflicts. The best fix seems to be bumping Teiid Spring Boot to a later version. The only downside is that later version of spring boot have switched to jakarta javax dependencies, so we get a lot of duplicate / different class warnings. We can ignore the errors/warning, try to exclude incoming dependencies from Teiid, or switch Teiid to use jakarta instead...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (TEIIDSB-198) Align with later 2.2.4 spring boot
by Steven Hawkins (Jira)
Steven Hawkins created TEIIDSB-198:
--------------------------------------
Summary: Align with later 2.2.4 spring boot
Key: TEIIDSB-198
URL: https://issues.redhat.com/browse/TEIIDSB-198
Project: Teiid Spring Boot
Issue Type: Task
Components: core
Reporter: Steven Hawkins
Fix For: 1.5.0
Due to the wildfly updates of TEIID-5859 that pull in a newer cxf and related dependencies, we end up with version conflicts. The best fix seems to be bumping Teiid Spring Boot to a later version. The only downside is that later version of spring boot have switched to jakarta javax dependencies, so we get a lot of duplicate / different class warnings. We can ignore the errors/warning, try to exclude incoming dependencies from Teiid, or switch Teiid to use jakarta instead...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (TEIID-5859) Upgrade to wildfly 19
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5859?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-5859:
---------------------------------------
Added the initial commit that updates the poms to 19.1. The only real problem is that there is an incompatibility between the wildfly jgroups and infinispan in the way that we're using infinispan. I added an override to downgrade jgroups.
> Upgrade to wildfly 19
> ---------------------
>
> Key: TEIID-5859
> URL: https://issues.redhat.com/browse/TEIID-5859
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits, Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.0
>
>
> We should pick up the latest wildfly 18+
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (TEIID-5950) Create an athena translator
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5950?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5950:
----------------------------------
Description: There have been several issues seen with athena using the jdbc ansi translator - subquery support and bind variables specifically. There should be a specific translator so that we can account for those better.
Original Estimate: 4 hours
Remaining Estimate: 4 hours
> Create an athena translator
> ---------------------------
>
> Key: TEIID-5950
> URL: https://issues.redhat.com/browse/TEIID-5950
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> There have been several issues seen with athena using the jdbc ansi translator - subquery support and bind variables specifically. There should be a specific translator so that we can account for those better.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months