March 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-117) Investigate to replace swagger UI

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-117?page=com.atlassian.jira.plug... ] Ramesh Reddy reassigned TEIIDSB-117: ------------------------------------ Assignee: (was: Ramesh Reddy) > Investigate to replace swagger UI > --------------------------------- > > Key: TEIIDSB-117 > URL: https://issues.redhat.com/browse/TEIIDSB-117 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Ramesh Reddy > Priority: Major > > Investigate to replace the Swagger UI with > https://atkawa7.github.io/httpsnippet/ > see a similar issue in Syndesis https://github.com/syndesisio/syndesis/issues/3948 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-109) Allow for the usage of the spring platform transaction manager in more scenarios

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-109?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-109: --------------------------------- Fix Version/s: (was: 1.4.0) > Allow for the usage of the spring platform transaction manager in more scenarios > -------------------------------------------------------------------------------- > > Key: TEIIDSB-109 > URL: https://issues.redhat.com/browse/TEIIDSB-109 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core > Reporter: Steven Hawkins > Priority: Major > > Unless an xa source is being used, we would ideally use the default platform transaction manager. This would map updates over multiple sources to best effort single phase commit. This will likely be the majority of our usage. > The problem is that the platform transaction manager doesn't directly support a suspend/resume concept that is needed for our remote pg/jdbc processing logic that allows the processing thread to detach from the current work when blocked and do something else. > It would be worth investigating if this functionality could be added to spring boot or if there is is some other approach that was missed with the initial investigation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-150) Micrometer spike

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-150?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-150: --------------------------------- Fix Version/s: 1.5.0 > Micrometer spike > ---------------- > > Key: TEIIDSB-150 > URL: https://issues.redhat.com/browse/TEIIDSB-150 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: core > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > > This work will wind up in Teiid spring boot (and even teiid), but the driver is from this project. We need to examine the level of effort of converting to micrometer rather than just jmx metrics for better spring integration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-52) Organize docs as much as possible into topics

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-52?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-52: ------------------------------------- With all the documentation work going on can we resolve this? > Organize docs as much as possible into topics > --------------------------------------------- > > Key: TEIIDSB-52 > URL: https://issues.redhat.com/browse/TEIIDSB-52 > Project: Teiid Spring Boot > Issue Type: Sub-task > Components: documentation > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > > To align with product documentation the docs need to be as topic (a particular dev/admin action) based as possible - rather than general subject areas. We also need to update anything listing steps to use a numbered list with as granular as possible steps. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-52) Organize docs as much as possible into topics

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-52?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-52: -------------------------------- Fix Version/s: 1.5.0 (was: 1.4.0) > Organize docs as much as possible into topics > --------------------------------------------- > > Key: TEIIDSB-52 > URL: https://issues.redhat.com/browse/TEIIDSB-52 > Project: Teiid Spring Boot > Issue Type: Sub-task > Components: documentation > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > > To align with product documentation the docs need to be as topic (a particular dev/admin action) based as possible - rather than general subject areas. We also need to update anything listing steps to use a numbered list with as granular as possible steps. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-163) Provide pooling for BaseConnectionFactory sources

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-163?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-163: --------------------------------- Fix Version/s: 1.5.0 (was: 1.4.0) > Provide pooling for BaseConnectionFactory sources > ------------------------------------------------- > > Key: TEIIDSB-163 > URL: https://issues.redhat.com/browse/TEIIDSB-163 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > > It will depend on the source and the cost of creating a connection, but in general we should provide pooling for connections rather than creating the for every operation. For example salesforce is a heavy weight connection. > The pooling will need to be tied into spring security or jca like logic to properly manage connections by identity once we re-establish that logic. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-169) JDG caching for multi-pod dv

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-169?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-169: --------------------------------- Fix Version/s: 1.5.0 > JDG caching for multi-pod dv > ---------------------------- > > Key: TEIIDSB-169 > URL: https://issues.redhat.com/browse/TEIIDSB-169 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: OpenShift > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > For multi-pod support we need to: > * Result set caching needs to directly write batches / results to JDG rather than relying upon on demand replication. > * replace the logic that detect failed materialization loads -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-172) Need to implement oauth2 and jwt auth in teiid spring boot

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-172?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-172: --------------------------------- Fix Version/s: 1.5.0 > Need to implement oauth2 and jwt auth in teiid spring boot > ---------------------------------------------------------- > > Key: TEIIDSB-172 > URL: https://issues.redhat.com/browse/TEIIDSB-172 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: datasource > Reporter: Renat Eskenin > Priority: Major > Fix For: 1.5.0 > > > We use oauth2 and jwt authentication for SalesForce and now in Teiid spring boot we have only user/password auth. > Please implement jwt and oauth2 authentications by spring properties. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-157) Support loading password credential from infinispan secret

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-157?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-157: --------------------------------- Fix Version/s: 1.5.0 (was: 1.4.0) > Support loading password credential from infinispan secret > ---------------------------------------------------------- > > Key: TEIIDSB-157 > URL: https://issues.redhat.com/browse/TEIIDSB-157 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: datasource > Reporter: Steven Hawkins > Priority: Major > Fix For: 1.5.0 > > Original Estimate: 5 hours > Time Spent: 2 hours > Remaining Estimate: 3 hours > > The infinispan operator generates a secret that contains a yaml file, which is where the developer password is stored. > There three approaches: > 1. for materialization assume that we will "own" the DataGrid instance such that we'll create and pass our own secret file for infinispan to use. In this case we'll know the password and can provide that to the connection factory via an env property. > 2. add logic to the connection factory to specify a "credential file" such that we'll parse the yaml from the given location (a mount of the secret) and find the appropriate credential for the given username (typically developer). > 3. ask the infinispan team to allow for easier consumption of the secret (a secret per user?) > To get things working with the example, I can take the first approach - but it will look a little convoluted. > In general 2 or 3 will be needed in scenarios where we expect to simply pick up existing credentials. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-42) Add a grafana dashboard example

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-42?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIIDSB-42: -------------------------------- Parent: (was: TEIIDSB-23) Issue Type: Feature Request (was: Sub-task) > Add a grafana dashboard example > ------------------------------- > > Key: TEIIDSB-42 > URL: https://issues.redhat.com/browse/TEIIDSB-42 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > > Building off of the prometheus metrics collection, we should provide a grafana dashboard. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2020