May 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5838) Add a vdb/source metadata load timeout

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5838?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5838: ---------------------------------- Fix Version/s: (was: 14.0) > Add a vdb/source metadata load timeout > -------------------------------------- > > Key: TEIID-5838 > URL: https://issues.redhat.com/browse/TEIID-5838 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 14.1 > > > Source vdb loads should timeout to prevent refresh and other issues. > Note: this may be implemented in core Teiid, in which case this issue will be moved. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5838) Add a vdb/source metadata load timeout

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5838?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5838: ---------------------------------- Fix Version/s: 14.1 > Add a vdb/source metadata load timeout > -------------------------------------- > > Key: TEIID-5838 > URL: https://issues.redhat.com/browse/TEIID-5838 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 14.0, 14.1 > > > Source vdb loads should timeout to prevent refresh and other issues. > Note: this may be implemented in core Teiid, in which case this issue will be moved. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5936) evaluate aws sdk for java for s3 support

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5936?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5936: ---------------------------------- Fix Version/s: 14.1 > evaluate aws sdk for java for s3 support > ---------------------------------------- > > Key: TEIID-5936 > URL: https://issues.redhat.com/browse/TEIID-5936 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 14.0, 14.1 > > > As an alternative to our existing support we should evaluate utilizing the sdk rather than providing our own processing logic. More than likely this will be a quicker path to things like s3 select support. However ceph seems to lag in s3 support (see TEIID-5935 and no s3 select support) so we'd have to compensate, make the metadata and/or the capabilities specific to the connection type. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5736) General odata function mapping

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5736?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5736: ---------------------------------- Fix Version/s: 14.1 > General odata function mapping > ------------------------------ > > Key: TEIID-5736 > URL: https://issues.redhat.com/browse/TEIID-5736 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Priority: Major > Fix For: 14.0, 14.1 > > > We are currently mapping procedures and functions defined by ddl to odata functions/actions. The latter is due that the function is represented in our system metadata as a procedure. We need to decide if all functions should be mapped. There's also the notion of a composable function that could be helpful. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[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 resolved TEIIDSB-192. ------------------------------------ Resolution: Done Marking this as resolved. The only thing that is not covered at the new alias names. [~rareddy] should we present these in the common doc set as translators or is there some place else you want to maintain a master list of alias names? > 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: 4 hours > Remaining Estimate: 0 minutes > > 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

1
0
0 / 0

[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 resolved TEIIDSB-198. ------------------------------------ Resolution: Done We're now aligned with 2.2.6, which updates the spring version, several other dependencies, and switches us to jakarta javax dependencies. Several managed dependencies were added for syndesis and other usage. > 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 > Time Spent: 6 hours > Remaining Estimate: 0 minutes > > 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

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-198) Align with 2.2.6 spring boot

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-198?focusedWorklogId=12450999&pa... ] Steven Hawkins logged work on TEIIDSB-198: ------------------------------------------ Author: Steven Hawkins Created on: 11/May/20 8:19 AM Start Date: 11/May/20 8:19 AM Worklog Time Spent: 1 hour Work Description: additional time for updates related to syndesis Issue Time Tracking ------------------- Time Spent: 7 hours (was: 6 hours) Worklog Id: (was: 12450999) > 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 > Time Spent: 7 hours > Remaining Estimate: 0 minutes > > 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

1
0
0 / 0

[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 resolved TEIID-5859. ----------------------------------- Resolution: Done Marking as resolved everything appears to be running as expected in arquillian. The doc AS version numbers were updated as well. > 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 > > Original Estimate: 1 day > Time Spent: 4 hours > Remaining Estimate: 4 hours > > We should pick up the latest wildfly 18+ -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-57) Provide Cassandra data source support

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-57?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIIDSB-57: ---------------------------------- Git Pull Request: https://github.com/teiid/teiid-spring-boot/pull/224 Sprint: DV Sprint 63 > Provide Cassandra data source support > ------------------------------------- > > Key: TEIIDSB-57 > URL: https://issues.redhat.com/browse/TEIIDSB-57 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Aditya Manglam Sharma > Priority: Major > Fix For: 1.5.0 > > > Provide data source support for Cassandra -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-197) Add a module for each external source

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-197?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-197: ---------------------------------------- > I believe you are too focused on the process improvement over the functionality, I am weighted more on functionality right now. >From my perspective there's no harm in making our lives as easy as possible down the road. > I saw deficiencies last time around Yes, once pushed. > Right now I am viewing this as crud work that is not bringing much functionality thus reluctance to go jump all over it You'll need to accept that considerations of design and technical debt must occur along side feature work. How it all gets captured and prioritized has a lot of flexibility. > Right now I am viewing this as crud work that is not bringing much functionality thus reluctance to go jump all over it Capturing an issue like this does not mean that it needs to be worked by you or in the near term. Since there are no design docs and little docs in general about the workings of the operator in regards to dependency handling at the very least issues like these help others understand what is there. > Add a module for each external source > ------------------------------------- > > Key: TEIIDSB-197 > URL: https://issues.redhat.com/browse/TEIIDSB-197 > Project: Teiid Spring Boot > Issue Type: Enhancement > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > > To simplify the logic in the operator each external source should be represented by a maven artifact - org.teiid:spring-data-x. Any dependency management would be handled in that module and not in the operator - to remove the need for a config file containing driver versions. Additionally property handling should be moved into Teiid Spring Boot such that the operator does not need to know what property prefix is expected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2020