May 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-55) Provide GoogleSheets support

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-55?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIIDSB-55: ----------------------------------- Assignee: Ramesh Reddy > Provide GoogleSheets support > ---------------------------- > > Key: TEIIDSB-55 > URL: https://issues.jboss.org/browse/TEIIDSB-55 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Provide data source support for Google Sheets. Must support the same authentication mechanism as Syndesis. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-83) Change odbc-enable to pg-enable

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-83?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIIDSB-83. ----------------------------------- Resolution: Done Updated to the more generic pg term. > Change odbc-enable to pg-enable > ------------------------------- > > Key: TEIIDSB-83 > URL: https://issues.jboss.org/browse/TEIIDSB-83 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core, documentation, examples > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.1.0 > > > Starting a fresh we should prefer the term pg over odbc as we support a range of pg client types. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-84) There needs to be an error page

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-84?page=com.atlassian.jira.plugin... ] Work on TEIIDSB-84 started by Steven Hawkins. --------------------------------------------- > There needs to be an error page > ------------------------------- > > Key: TEIIDSB-84 > URL: https://issues.jboss.org/browse/TEIIDSB-84 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.1.0 > > > If you try a url, such as /foo it results in a lengthy log: > 2019-04-30 15:20:14.247 ERROR 14280 --- [nio-8080-exec-2] o.a.c.c.C.[Tomcat].[localhost] : Exception Processing ErrorPage[errorCode=0, location=/error] > javax.servlet.ServletException: Circular view path [error]: would dispatch back to the current handler URL [/error] again. Check your ViewResolver setup! (Hint: This may be the result of an unspecified view, due to default view name generation.) > at org.springframework.web.servlet.view.InternalResourceView.prepareForRendering(InternalResourceView.java:209) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELEASE] > at org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:147) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELEASE] > at org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:316) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELEASE] > at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1370) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELE... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-84) There needs to be an error page

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-84?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIIDSB-84: ----------------------------------- Assignee: Steven Hawkins (was: Ramesh Reddy) > There needs to be an error page > ------------------------------- > > Key: TEIIDSB-84 > URL: https://issues.jboss.org/browse/TEIIDSB-84 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.1.0 > > > If you try a url, such as /foo it results in a lengthy log: > 2019-04-30 15:20:14.247 ERROR 14280 --- [nio-8080-exec-2] o.a.c.c.C.[Tomcat].[localhost] : Exception Processing ErrorPage[errorCode=0, location=/error] > javax.servlet.ServletException: Circular view path [error]: would dispatch back to the current handler URL [/error] again. Check your ViewResolver setup! (Hint: This may be the result of an unspecified view, due to default view name generation.) > at org.springframework.web.servlet.view.InternalResourceView.prepareForRendering(InternalResourceView.java:209) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELEASE] > at org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:147) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELEASE] > at org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:316) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELEASE] > at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1370) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELE... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-84) There needs to be an error page

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-84?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIIDSB-84: ----------------------------------- Assignee: Ramesh Reddy > There needs to be an error page > ------------------------------- > > Key: TEIIDSB-84 > URL: https://issues.jboss.org/browse/TEIIDSB-84 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > If you try a url, such as /foo it results in a lengthy log: > 2019-04-30 15:20:14.247 ERROR 14280 --- [nio-8080-exec-2] o.a.c.c.C.[Tomcat].[localhost] : Exception Processing ErrorPage[errorCode=0, location=/error] > javax.servlet.ServletException: Circular view path [error]: would dispatch back to the current handler URL [/error] again. Check your ViewResolver setup! (Hint: This may be the result of an unspecified view, due to default view name generation.) > at org.springframework.web.servlet.view.InternalResourceView.prepareForRendering(InternalResourceView.java:209) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELEASE] > at org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:147) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELEASE] > at org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:316) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELEASE] > at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1370) ~[spring-webmvc-5.1.4.RELEASE.jar!/:5.1.4.RELE... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5704) Support openapi 3 sources

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5704?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5704: ---------------------------------- Fix Version/s: 12.3 (was: 12.x) > Support openapi 3 sources > ------------------------- > > Key: TEIID-5704 > URL: https://issues.jboss.org/browse/TEIID-5704 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > It seems like a good idea to introduce a new translator, rather than trying to fit openapi 3 support onto the swagger translator - as the io.swagger libraries and a lot of logic will be different. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-85) Remove the need for an odata role

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-85?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIIDSB-85. ----------------------------------- Resolution: Done Removed the role requirement. Will be removed from the example as part of a larger re-work. > Remove the need for an odata role > --------------------------------- > > Key: TEIIDSB-85 > URL: https://issues.jboss.org/browse/TEIIDSB-85 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.1.0 > > > The odata access role was carried forward from Teiid to Teiid Spring Boot. We should rethink this. > I think the reason it was originally added was for installs that were not using data roles it ensured that odata access was not wide open. It also introduced the complexity that it could be using a different security domain that the default. > It's simplest to just remove the role requirement. As we've refined things we now are using the same realm through out and a single client for both odata and pg/jdbc access. Since it's very easy to add grant all roles to properly permissioned users or simple grant all read-only access, it does not seem necessary to further restrict odata access at the teiid level. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-85) Remove the need for an odata role

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-85?page=com.atlassian.jira.plugin... ] Work on TEIIDSB-85 started by Steven Hawkins. --------------------------------------------- > Remove the need for an odata role > --------------------------------- > > Key: TEIIDSB-85 > URL: https://issues.jboss.org/browse/TEIIDSB-85 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.1.0 > > > The odata access role was carried forward from Teiid to Teiid Spring Boot. We should rethink this. > I think the reason it was originally added was for installs that were not using data roles it ensured that odata access was not wide open. It also introduced the complexity that it could be using a different security domain that the default. > It's simplest to just remove the role requirement. As we've refined things we now are using the same realm through out and a single client for both odata and pg/jdbc access. Since it's very easy to add grant all roles to properly permissioned users or simple grant all read-only access, it does not seem necessary to further restrict odata access at the teiid level. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-85) Remove the need for an odata role

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-85?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIIDSB-85: ---------------------------------- Description: The odata access role was carried forward from Teiid to Teiid Spring Boot. We should rethink this. I think the reason it was originally added was for installs that were not using data roles it ensured that odata access was not wide open. It also introduced the complexity that it could be using a different security domain that the default. It's simplest to just remove the role requirement. As we've refined things we now are using the same realm through out and a single client for both odata and pg/jdbc access. Since it's very easy to add grant all roles to properly permissioned users or simple grant all read-only access, it does not seem necessary to further restrict odata access at the teiid level. was: The odata access role was carried forward from Teiid to Teiid Spring Boot. We should rethink this. I think the reason it was originally added was for installs that were not using data roles it ensured that odata access was not wide open. It also introduced the complexity that it could be using a different security domain that the default. It's simplest to just remove the role requirement. As we've refined things we now are using the same realm through out and a single client for both odata and pg/jdbc access. Since it's very easy to add grant all roles to properly permissioned users or simple grant all read-only access, it does not seem necessary to further restrict odata access at the teiid level. 2. Since we allowed different security domains > Remove the need for an odata role > --------------------------------- > > Key: TEIIDSB-85 > URL: https://issues.jboss.org/browse/TEIIDSB-85 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.1.0 > > > The odata access role was carried forward from Teiid to Teiid Spring Boot. We should rethink this. > I think the reason it was originally added was for installs that were not using data roles it ensured that odata access was not wide open. It also introduced the complexity that it could be using a different security domain that the default. > It's simplest to just remove the role requirement. As we've refined things we now are using the same realm through out and a single client for both odata and pg/jdbc access. Since it's very easy to add grant all roles to properly permissioned users or simple grant all read-only access, it does not seem necessary to further restrict odata access at the teiid level. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-85) Remove the need for an odata role

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-85: ------------------------------------- Summary: Remove the need for an odata role Key: TEIIDSB-85 URL: https://issues.jboss.org/browse/TEIIDSB-85 Project: Teiid Spring Boot Issue Type: Quality Risk Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 1.1.0 The odata access role was carried forward from Teiid to Teiid Spring Boot. We should rethink this. I think the reason it was originally added was for installs that were not using data roles it ensured that odata access was not wide open. It also introduced the complexity that it could be using a different security domain that the default. It's simplest to just remove the role requirement. As we've refined things we now are using the same realm through out and a single client for both odata and pg/jdbc access. Since it's very easy to add grant all roles to properly permissioned users or simple grant all read-only access, it does not seem necessary to further restrict odata access at the teiid level. 2. Since we allowed different security domains -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2019