[JBoss JIRA] (TEIID-5351) Upgrade to WildFly 14
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5351?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5351:
-------------------------------------
previously we only had versions that are overriden or new ones introduced in the Teiid in the parent pom. Only those should make it into teiid bom. Also, I find it too tedious to do the bom updates when a version updates are needed.
> Upgrade to WildFly 14
> ---------------------
>
> Key: TEIID-5351
> URL: https://issues.jboss.org/browse/TEIID-5351
> Project: Teiid
> Issue Type: Task
> Components: Server
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 12.x
>
>
> We should move to WildFly 13, which should be at GA by the Teiid 11.0 release.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (TEIID-5351) Upgrade to WildFly 14
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5351?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5351:
---------------------------------------
I'll update this issue with some prs or commits on branches of the integration bom / teiid project. Observations:
- there seems to be few configuration api changes to account for. perhaps more backwards compatibility was added since the first look at wildfly 13.
- jgroups api has changed. we would need to re-fork the replication logic or remove it. Given TEIID-5476 and the lack of containerized support, we should probably opt for removal.
- infinispan's expectations for the configuration file have changed, the old one is no longer valid
- several dependencies have changed, but overall it seems pretty stable. When reconciling to a new version, I don't see a quick way to determine which dependencies actually need versions specified. I'll probably create a script of something to quickly compare between or bom and the parent.
> Upgrade to WildFly 14
> ---------------------
>
> Key: TEIID-5351
> URL: https://issues.jboss.org/browse/TEIID-5351
> Project: Teiid
> Issue Type: Task
> Components: Server
> Reporter: Steven Hawkins
> Priority: Major
> Fix For: 12.x
>
>
> We should move to WildFly 13, which should be at GA by the Teiid 11.0 release.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (TEIID-2542) Utilize Teiid internal resultset buffering as a materialization mechanism to Infinspan
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-2542?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2542:
----------------------------------
Fix Version/s: 12.x
(was: 11.x)
> Utilize Teiid internal resultset buffering as a materialization mechanism to Infinspan
> --------------------------------------------------------------------------------------
>
> Key: TEIID-2542
> URL: https://issues.jboss.org/browse/TEIID-2542
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Van Halbert
> Priority: Major
> Fix For: 12.x
>
>
> Add support for materialization to Infinispan by utilizing the Teiid internal buffering mechanism to Infinispan. Suggestion, turn that mechanism into a translator that can read/write to Infinispan.
> Pro's:
> - distributed data-grid fail-over and HA could be less costly than trying to do this with a database.
> - improved performance where each Infinispan instance could placed closer to its' users.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (TEIID-2052) Add Problem/Resolution to query problem using the query plan
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-2052?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2052:
----------------------------------
Fix Version/s: 12.x
(was: 11.x)
> Add Problem/Resolution to query problem using the query plan
> ------------------------------------------------------------
>
> Key: TEIID-2052
> URL: https://issues.jboss.org/browse/TEIID-2052
> Project: Teiid
> Issue Type: Enhancement
> Components: Documentation
> Affects Versions: 7.7.1
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Optional
> Fix For: 12.x
>
> Attachments: INClauseNotPushedDown.odt
>
>
> Adding content that could be used for query problem resolution. The initial attachment does the following:
> - states the query problem (i.e., not pushing down the "IN" clause)
> - provides the query plan (and debug log) for the query being submitted
> - provides recommendations for resolving the problem
> - then indicates how this problem was resolved and what the resulting query plan / debug log
> The idea here is to continue to add other problem scenarios so that this information is really useful for resolving issues.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months