March 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4837) Add ability to measure caching at the VDB level

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-4837?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-4837: ---------------------------------- Fix Version/s: (was: 13.x) > Add ability to measure caching at the VDB level > ----------------------------------------------- > > Key: TEIID-4837 > URL: https://issues.redhat.com/browse/TEIID-4837 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 11.x > Reporter: Van Halbert > Priority: Major > > Add ability to measure caching statistics at the VDB level -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2819) Use Oauth SAML Bearer Assertion Flow

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-2819?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-2819: ---------------------------------- Fix Version/s: (was: 13.x) > Use Oauth SAML Bearer Assertion Flow > ------------------------------------ > > Key: TEIID-2819 > URL: https://issues.redhat.com/browse/TEIID-2819 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Major > > I can secure my mobile and cloud applications? > Consider doing SAML first and Oauth later – the use cases are the same, the implementation is different > Link - https://help.salesforce.com/apex/HTViewHelpDoc?id=remoteaccess_oauth_SAML... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5920) Update dependencies in order to build in PNC for the .next release

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIID-5920?page=com.atlassian.jira.plugi... ] Van Halbert edited comment on TEIID-5920 at 3/23/20 9:10 PM: ------------------------------------------------------------- [ERROR] Found a problem with the dependency javax.validation:validation-api Resolved version is 2.0.1.Final Version 2.0.1.Final-redhat-1 was expected by artifact: org.teiid.connectors:translator-openapi Will be updating teiid to 201.Final-redhat-1. - Changing to use the pipeline overrides, as this is pulled from MRCC. No change to teiid is now targeted for this issue. Currently testing thru PNC build. (this didn't work in the realignment) - the way that currently works is to add the validation-api exclusion to the translator-openapi dependency in teiid-spring-boot - [PR request | https://github.com/teiid/teiid-spring-boot/pull/198] was (Author: rhn-engineering-vhalbert): [ERROR] Found a problem with the dependency javax.validation:validation-api Resolved version is 2.0.1.Final Version 2.0.1.Final-redhat-1 was expected by artifact: org.teiid.connectors:translator-openapi Will be updating teiid to 201.Final-redhat-1. - Changing to use the pipeline overrides, as this is pulled from MRCC. No change to teiid is now targeted for this issue. Currently testing thru PNC build. (this didn't work in the realignment) - the way that currently works is to add the validation-api exclusion to the translator-openapi dependency in teiid-spring-boot - [PR request | https://github.com/teiid/teiid-spring-boot/pull/198} > Update dependencies in order to build in PNC for the .next release > ------------------------------------------------------------------- > > Key: TEIID-5920 > URL: https://issues.redhat.com/browse/TEIID-5920 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Affects Versions: 13.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > In order to build in PNC, certain dependency alignments are required in order to build. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5920) Update dependencies in order to build in PNC for the .next release

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIID-5920?page=com.atlassian.jira.plugi... ] Van Halbert edited comment on TEIID-5920 at 3/23/20 9:10 PM: ------------------------------------------------------------- [ERROR] Found a problem with the dependency javax.validation:validation-api Resolved version is 2.0.1.Final Version 2.0.1.Final-redhat-1 was expected by artifact: org.teiid.connectors:translator-openapi Will be updating teiid to 201.Final-redhat-1. - Changing to use the pipeline overrides, as this is pulled from MRCC. No change to teiid is now targeted for this issue. Currently testing thru PNC build. (this didn't work in the realignment) - the way that currently works is to add the validation-api exclusion to the translator-openapi dependency in teiid-spring-boot - [PR request | https://github.com/teiid/teiid-spring-boot/pull/198} was (Author: rhn-engineering-vhalbert): [ERROR] Found a problem with the dependency javax.validation:validation-api Resolved version is 2.0.1.Final Version 2.0.1.Final-redhat-1 was expected by artifact: org.teiid.connectors:translator-openapi Will be updating teiid to 201.Final-redhat-1. - Changing to use the pipeline overrides, as this is pulled from MRCC. No change to teiid is now targeted for this issue. Currently testing thru PNC build. (this didn't work in the realignment) - the way that currently works is to add the validation-api exclusion to the translator-openapi dependency in teiid-spring-boot > Update dependencies in order to build in PNC for the .next release > ------------------------------------------------------------------- > > Key: TEIID-5920 > URL: https://issues.redhat.com/browse/TEIID-5920 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Affects Versions: 13.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > In order to build in PNC, certain dependency alignments are required in order to build. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5920) Update dependencies in order to build in PNC for the .next release

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIID-5920?page=com.atlassian.jira.plugi... ] Van Halbert edited comment on TEIID-5920 at 3/23/20 8:53 PM: ------------------------------------------------------------- [ERROR] Found a problem with the dependency javax.validation:validation-api Resolved version is 2.0.1.Final Version 2.0.1.Final-redhat-1 was expected by artifact: org.teiid.connectors:translator-openapi Will be updating teiid to 201.Final-redhat-1. - Changing to use the pipeline overrides, as this is pulled from MRCC. No change to teiid is now targeted for this issue. Currently testing thru PNC build. (this didn't work in the realignment) - the way that currently works is to add the validation-api exclusion to the translator-openapi dependency in teiid-spring-boot was (Author: rhn-engineering-vhalbert): [ERROR] Found a problem with the dependency javax.validation:validation-api Resolved version is 2.0.1.Final Version 2.0.1.Final-redhat-1 was expected by artifact: org.teiid.connectors:translator-openapi Will be updating teiid to 201.Final-redhat-1. - Changing to use the pipeline overrides, as this is pulled from MRCC. No change to teiid is now targeted for this issue. Currently testing thru PNC build. > Update dependencies in order to build in PNC for the .next release > ------------------------------------------------------------------- > > Key: TEIID-5920 > URL: https://issues.redhat.com/browse/TEIID-5920 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Affects Versions: 13.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > In order to build in PNC, certain dependency alignments are required in order to build. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-170) Automate materialization to JDG

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-170?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-170: --------------------------------- Sprint: DV Sprint 60, DV Sprint 61 (was: DV Sprint 60) > Automate materialization to JDG > ------------------------------- > > Key: TEIIDSB-170 > URL: https://issues.redhat.com/browse/TEIIDSB-170 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: OpenShift > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > Original Estimate: 1 week > Time Spent: 1 hour > Remaining Estimate: 4 days, 7 hours > > Create an internal materialization replacement needs that is turnkey materialization to JDG (little to no user setup required) > - the operator may create the infinispan cluster if needed > - the status table and internal representation of the materialization target would be setup automatically > For the user this would be as simple marking a view as materialized and then it would be populated in jdg upon deployment. They would not have any concerns with cache naming, status tables, etc. > For simplicity the initial version would make a similar assumption to the current internal logic - it is for only a specific vdb. If the vdb cr is modified, then it's expected that the cache would be recreated. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 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: --------------------------------- Sprint: DV Sprint 61 > 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, 2 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: --------------------------------- Sprint: DV Sprint 60, DV Sprint 61 (was: DV Sprint 60) > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-179) VDB Plugin needs to preserve the order of the VDB-Imports

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-179?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIIDSB-179: -------------------------------------- Right now it does not give correct guidance with the error, also I wanted to see this work when full metadata is supplied. Another lofty goal I am thinking is your suggestion from before to explore the metadata fetch during this call, especially when we this process is running on Openshift we have all the config and code to make this possible. We should look into that, albeit incrementally. This serialized parsing should help with that too. > VDB Plugin needs to preserve the order of the VDB-Imports > --------------------------------------------------------- > > Key: TEIIDSB-179 > URL: https://issues.redhat.com/browse/TEIIDSB-179 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > > The parsing of the VDB file needs to be done sequentially one statement at a time so that we can inline the VDB-Import in the order they are defined, and this also sequences any IMPORT FOREIGN SCHEMA statements in the order they are expected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-179) VDB Plugin needs to preserve the order of the VDB-Imports

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-179?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-179: ---------------------------------------- If we are generally disallowing alter drop, that somewhat simplifies this problem for import foreign schema. It's still nice the preserve the order of everything to account for variations in when we resolve objects - anything that has logic in the parser needs things to be in the same relative order. However since we've got most things still being handled in the metadata validator there aren't as many places that we need to worry about. > VDB Plugin needs to preserve the order of the VDB-Imports > --------------------------------------------------------- > > Key: TEIIDSB-179 > URL: https://issues.redhat.com/browse/TEIIDSB-179 > Project: Teiid Spring Boot > Issue Type: Enhancement > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > > The parsing of the VDB file needs to be done sequentially one statement at a time so that we can inline the VDB-Import in the order they are defined, and this also sequences any IMPORT FOREIGN SCHEMA statements in the order they are expected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2020