February 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5662) Add option to Migration Utility to write to file

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5662?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5662: --------------------------------------- So the intent is to add a vdb-migration under teiid-openshift-examples? > Add option to Migration Utility to write to file > ------------------------------------------------ > > Key: TEIID-5662 > URL: https://issues.jboss.org/browse/TEIID-5662 > Project: Teiid > Issue Type: Feature Request > Components: Quick Starts, Tooling > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > Add an option to the Migration Utility for writing the converted vdb to a file, which could include the path to persist it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5662) Add option to Migration Utility to write to file

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5662?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5662. ----------------------------------- Fix Version/s: 12.1 Resolution: Done [~rhn-engineering-vhalbert] Let's start a doc page on this somewhere. > Add option to Migration Utility to write to file > ------------------------------------------------ > > Key: TEIID-5662 > URL: https://issues.jboss.org/browse/TEIID-5662 > Project: Teiid > Issue Type: Feature Request > Components: Quick Starts, Tooling > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 12.1 > > > Add an option to the Migration Utility for writing the converted vdb to a file, which could include the path to persist it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-40) define logging options

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-40?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-40: --------------------------------------- See https://github.com/shawkins/teiid-openshift-examples/commit/a3e6b695d16e2... To use logstash json formatting to just the console log needs an encoding jar dependency and a logback-spring.xml configuration file. There are options to have logback send messages to logstash, but in theory fluentd will be responsible for that. [~rareddy] You can entertain separating this into it's own demo, but until we have this working end-to-end with kibana it won't be very interesting. > define logging options > ---------------------- > > Key: TEIIDSB-40 > URL: https://issues.jboss.org/browse/TEIIDSB-40 > Project: Teiid Spring Boot > Issue Type: Sub-task > Components: OpenShift > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.0.3 > > > It looks like the preferred mechanism with spring boot is to use: > https://github.com/logstash/logstash-logback-encoder > This should make it easier for the aggregate container logging to use the container logs. I'll validate this and update the example appropriately - which we could create a parallel to prometheus for the logging stack / kibana. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5665) Make teiid-metadata optional for the engine

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5665?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5665: ------------------------------------- Double checked in spring boot, did not see the explicit dependency. > Make teiid-metadata optional for the engine > ------------------------------------------- > > Key: TEIID-5665 > URL: https://issues.jboss.org/browse/TEIID-5665 > Project: Teiid > Issue Type: Task > Components: Embedded > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > The metadata jar is only for support of .index vdbs - it does not need to be a compile dependency and any usage in embedded should need an explicit dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5665) Make teiid-metadata optional for the engine

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5665?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5665. ----------------------------------- Resolution: Done Changed to a test dependency and updated the embedded guide. > Make teiid-metadata optional for the engine > ------------------------------------------- > > Key: TEIID-5665 > URL: https://issues.jboss.org/browse/TEIID-5665 > Project: Teiid > Issue Type: Task > Components: Embedded > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > The metadata jar is only for support of .index vdbs - it does not need to be a compile dependency and any usage in embedded should need an explicit dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5665) Make teiid-metadata optional for the engine

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5665?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5665: --------------------------------------- Unless you have an explicit dependency, this should fix it on the spring boot side. > Make teiid-metadata optional for the engine > ------------------------------------------- > > Key: TEIID-5665 > URL: https://issues.jboss.org/browse/TEIID-5665 > Project: Teiid > Issue Type: Task > Components: Embedded > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > The metadata jar is only for support of .index vdbs - it does not need to be a compile dependency and any usage in embedded should need an explicit dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5662) Add option to Migration Utility to write to file

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5662?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5662: ------------------------------- Component/s: Quick Starts > Add option to Migration Utility to write to file > ------------------------------------------------ > > Key: TEIID-5662 > URL: https://issues.jboss.org/browse/TEIID-5662 > Project: Teiid > Issue Type: Feature Request > Components: Quick Starts, Tooling > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > Add an option to the Migration Utility for writing the converted vdb to a file, which could include the path to persist it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-34) Support Keycloak based OAuth authentication for OData

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-34?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-34. --------------------------------- Resolution: Done There were more than few things that were wrong in the previous commit. * The security-context was being created, but wrongfully assumed it was being associated with the current thread during the 'createSession' call. * Subject with Role names was being built wrong order than Teiid expects. Fixed that. * Since we are using "spring-security", give the security help a new security-domain name and use that elsewhere such that that will be used. Note that, in the container world, since we are using single VDB per container VDB level security domain is not workable. Maybe we should ignore this during the migration of the .vdb to .DDL if one is set. * Also using correct baseName if security-context is available during the Teiid's createSession call. * The authentication order in Web Interceptors was wrong. The auth filter needs to come before the odata filter. > Support Keycloak based OAuth authentication for OData > ----------------------------------------------------- > > Key: TEIIDSB-34 > URL: https://issues.jboss.org/browse/TEIIDSB-34 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.0.3 > > > Provide Keycloak based oAuth2 authentication on top of OData API. This needs to be an optional feature either exposed through a flag or starter project in the pom.xml file. > The scope in the OAuth needs to be used as the roles in the Teiid (this is how legacy Teiid mapped) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-34) Support Keycloak based OAuth authentication for OData

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-34?page=com.atlassian.jira.plugin... ] Ramesh Reddy reopened TEIIDSB-34: --------------------------------- > Support Keycloak based OAuth authentication for OData > ----------------------------------------------------- > > Key: TEIIDSB-34 > URL: https://issues.jboss.org/browse/TEIIDSB-34 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.0.3 > > > Provide Keycloak based oAuth2 authentication on top of OData API. This needs to be an optional feature either exposed through a flag or starter project in the pom.xml file. > The scope in the OAuth needs to be used as the roles in the Teiid (this is how legacy Teiid mapped) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5665) Make teiid-metadata optional for the engine

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5665?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-5665 at 2/20/19 5:25 PM: -------------------------------------------------------------- Did not realize that, once you have this changed to the engine can also log one JIRA for spring boot. I will remove it there, or do it as part of this JIRA was (Author: rareddy): Did not realize that, once you have this changed to the engine can also log one JIRA for spring boot. I will remove it there. > Make teiid-metadata optional for the engine > ------------------------------------------- > > Key: TEIID-5665 > URL: https://issues.jboss.org/browse/TEIID-5665 > Project: Teiid > Issue Type: Task > Components: Embedded > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > The metadata jar is only for support of .index vdbs - it does not need to be a compile dependency and any usage in embedded should need an explicit dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2019