June 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5729) Introduce mechanism or option to allow for mapping of side effect free Teiid procedures to ODATA functions, and actions if procedure has side effects

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5729?page=com.atlassian.jira.plugin... ] Work on TEIID-5729 started by Steven Hawkins. --------------------------------------------- > Introduce mechanism or option to allow for mapping of side effect free Teiid procedures to ODATA functions, and actions if procedure has side effects > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-5729 > URL: https://issues.jboss.org/browse/TEIID-5729 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > This is a follow up regarding https://issues.jboss.org/browse/TEIID-5725 > As discussed there, Teiid currently does not map virtual procedures and functions to odata functions and procedures according to the notion of "side effect free" > Please introduce a mechanism to allow for a mapping according to adequate odata semantics. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5757) Remove the need for the odata role

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5757?page=com.atlassian.jira.plugin... ] Work on TEIID-5757 started by Steven Hawkins. --------------------------------------------- > Remove the need for the odata role > ---------------------------------- > > Key: TEIID-5757 > URL: https://issues.jboss.org/browse/TEIID-5757 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > Similar to TEIIDSB-85 the rationale for having an odata role no longer seems valid. It will simplify usage if that is no longer required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-62) OpenApi 3.0 Support for OData

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-62?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-62: --------------------------------------- > That said - my suggestion would be to follow this: https://restfulapi.net/versioning/ Seems like we need some standard. Unless we know that users can't / won't use the version header for their own api versioning we can't co-opt it. As you'd need to specify both: Accept: application/x-yaml;version=1.2.3;openapi=3.0.0 > OpenApi 3.0 Support for OData > ----------------------------- > > Key: TEIIDSB-62 > URL: https://issues.jboss.org/browse/TEIIDSB-62 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Support OpenAPI 3.0 document generation with OData service -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-103) Support vdb and/or classpath resources

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-103?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIIDSB-103: ---------------------------------------- Yes, it looks for the explicit vdb, then .ddl, then .vdb > Support vdb and/or classpath resources > -------------------------------------- > > Key: TEIIDSB-103 > URL: https://issues.jboss.org/browse/TEIIDSB-103 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.2.0 > > > The loading logic for a .vdb artifact does not create the associated vdb resources, so things like the ddl-file metadata repo cannot be used. We should probably support that, and in general may consider supporting a classpath based resource mechanism now that we have unified classloader. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-103) Support vdb and/or classpath resources

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-103?page=com.atlassian.jira.plugi... ] Ramesh Reddy commented on TEIIDSB-103: -------------------------------------- I thought it will check classpath in the below order # teiid.ddl # teiid.vdb (with DDL based Zip Archive) > Support vdb and/or classpath resources > -------------------------------------- > > Key: TEIIDSB-103 > URL: https://issues.jboss.org/browse/TEIIDSB-103 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.2.0 > > > The loading logic for a .vdb artifact does not create the associated vdb resources, so things like the ddl-file metadata repo cannot be used. We should probably support that, and in general may consider supporting a classpath based resource mechanism now that we have unified classloader. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-62) OpenApi 3.0 Support for OData

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-62?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-62: ------------------------------------- Per Eric.W there is no standard, but recommends below, if we can do this change for 12.2.1 then we can pull in to Teiid Spring Boot. I would say, by default without accepts header default to 2.0, then next versions when 3.0 support comes in, we can switch the default around. That said - my suggestion would be to follow this: https://restfulapi.net/versioning/ REST API Versioning Guide – REST API Tutorial REST API Versioning Guide – REST API Tutorial restfulapi.net See the section labeled "Versioning using Accept header" So in your case it could be: Accept: application/json;version=3.0.2 Accept: application/json;version=2.0 Accept: application/x-yaml;version=3.0.2 Accept: application/x-yaml;version=2.0 > OpenApi 3.0 Support for OData > ----------------------------- > > Key: TEIIDSB-62 > URL: https://issues.jboss.org/browse/TEIIDSB-62 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Support OpenAPI 3.0 document generation with OData service -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-103) Support vdb and/or classpath resources

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-103?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIIDSB-103. ------------------------------------ Resolution: Done Added vdb resource support for .vdb artifacts. We can open another issue if we want to support a classpath based mechanism for .ddl. Also updated the logic so that teiid.vdb is a default artifact. > Support vdb and/or classpath resources > -------------------------------------- > > Key: TEIIDSB-103 > URL: https://issues.jboss.org/browse/TEIIDSB-103 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.2.0 > > > The loading logic for a .vdb artifact does not create the associated vdb resources, so things like the ddl-file metadata repo cannot be used. We should probably support that, and in general may consider supporting a classpath based resource mechanism now that we have unified classloader. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-62) OpenApi 3.0 Support for OData

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-62?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-62: --------------------------------------- > For time being for 7.4 can we map both openapi.json and swagger.json to version 2.0. 3scale does not have support for version 3 yet. Maybe per Eric W, support 3 only by the version tag on the "Accepts" header? I'd vote for openapi.json supporting the accept header. Where is that documented? > OpenApi 3.0 Support for OData > ----------------------------- > > Key: TEIIDSB-62 > URL: https://issues.jboss.org/browse/TEIIDSB-62 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Support OpenAPI 3.0 document generation with OData service -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-62) OpenApi 3.0 Support for OData

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-62?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-62: ------------------------------------- [~shawkins] For time being for 7.4 can we map both openapi.json and swagger.json to version 2.0. 3scale does not have support for version 3 yet. Maybe per Eric W, support 3 only by the version tag on the "Accepts" header? > OpenApi 3.0 Support for OData > ----------------------------- > > Key: TEIIDSB-62 > URL: https://issues.jboss.org/browse/TEIIDSB-62 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Support OpenAPI 3.0 document generation with OData service -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5762) Update security configuration to elytron

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5762?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5762: ---------------------------------- Fix Version/s: 13.0 (was: 12.3) Summary: Update security configuration to elytron (was: Modernize the teiid configuration) > Update security configuration to elytron > ---------------------------------------- > > Key: TEIID-5762 > URL: https://issues.jboss.org/browse/TEIID-5762 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.0 > > > The Teiid configuration is based upon an out-dated version of the wildfly config. It should be brought up-to-date. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2019