May 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5545) Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5545. ----------------------------------- Resolution: Done Included with the 4.6 upgrade. > Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header > -------------------------------------------------------------------------------------------------------- > > Key: TEIID-5545 > URL: https://issues.jboss.org/browse/TEIID-5545 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 12.2 > > > When using Teiid together with SAPUI5/OpenUI5 Odata V4 model, batch processing does not work as Teiid rejects the "Accept: multipart/mixed" header. The issue has been described in > https://developer.jboss.org/message/986421#986421 > It has been stated that Olingo in general does support multipart messages and it was recommended to remove the header from the request. > https://developer.jboss.org/message/986425#986425 > Unfortunately this seems to be not easily possible when using the SAPUI5 framework. I addressed the issue in the SAPUI5 forum under the following issue: > https://github.com/SAP/openui5/issues/2288 > The result of this discussion was, that the header is valid for the send content. As I am no expert in the topic I do not really have an opinion on that. However, > https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html > suggests that the header is required. So I am not sure if it is correct or an error to reject the message. However, if Olingo can process the content, it would be great to have a fix for the accept header, or alternatively a config option to enable handling of the Accept header in a way that Olingo processes these data. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-4) Provide rest access with SpringBoot

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-4?page=com.atlassian.jira.plugin.... ] Ramesh Reddy commented on TEIIDSB-4: ------------------------------------ The way I started this process is to introduce a maven plugin called "vdb-code-generator" which during the build time introspects the VDB and if it finds the REST specific metadata on the VDB it will generate the Spring REST API code for. The current implementation is par with what is available in WildFly version. This needs to be further improved to handle the return type generation. > Provide rest access with SpringBoot > ----------------------------------- > > Key: TEIIDSB-4 > URL: https://issues.jboss.org/browse/TEIIDSB-4 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > > The current rest access layer is based upon the generation of a war with deployment hooks in wildfly. There should be a build-time or similar mechanism to expose rest with spring boot. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-63) Support Keycloak based OpenID authentication for OData Through 3scale

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-63?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIIDSB-63. --------------------------------- Resolution: Done The solution has been documented in the examples and had been shown in the demo. Any further work involving the automation needs to be separate from this effort. > Support Keycloak based OpenID authentication for OData Through 3scale > --------------------------------------------------------------------- > > Key: TEIIDSB-63 > URL: https://issues.jboss.org/browse/TEIIDSB-63 > Project: Teiid Spring Boot > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > Support the authentication for OData through 3scale -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5735) Update Olingo library to 4.6.0

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5735?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5735: --------------------------------------- Looking at things further BatchRequest.processChangeSet does it's own handling of the error case. I'll validate exactly what the user may have been seeing. > Update Olingo library to 4.6.0 > ------------------------------ > > Key: TEIID-5735 > URL: https://issues.jboss.org/browse/TEIID-5735 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.2 > > > Apache Olingo 4.6 released, to pick up changes update to the new version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5735) Update Olingo library to 4.6.0

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5735?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-5735. --------------------------------- Resolution: Done Upgraded to 4.6.0 [~shawkins] unfortunately no as the release is already in maven, either we can introduce a patch layer in Teiid or work to see we can ask for 4.6.1 soon. > Update Olingo library to 4.6.0 > ------------------------------ > > Key: TEIID-5735 > URL: https://issues.jboss.org/browse/TEIID-5735 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.2 > > > Apache Olingo 4.6 released, to pick up changes update to the new version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-86) Plans for secure socket transports

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-86?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-86: --------------------------------------- To expand on pg. To do sni you must be configure a passthrough route. To do edge termination requires a standard http service on the backend. pg is not end-to-end encryption. Add tls is part of of there protocol, so passthrough won't work. I'll investigate tls with sni for Teiid JDBC though. > Plans for secure socket transports > ---------------------------------- > > Key: TEIIDSB-86 > URL: https://issues.jboss.org/browse/TEIIDSB-86 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.1.0 > > > The Teiid Spring Boot configuration allows for only non-secured pg / JDBC socket transports. For external client scenarios and even for varying degrees of compliance with intra-cluster traffic, a secure layer may be required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5513) Fully automate release

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5513?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5513: ---------------------------------- Fix Version/s: 12.3 (was: 12.2) Did not make further progress on this in 12.2. Will need to likely revisit after the teiid / teiid-wildfly split in Teiid 13. > Fully automate release > ---------------------- > > Key: TEIID-5513 > URL: https://issues.jboss.org/browse/TEIID-5513 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > We should add a fully automated release on the creation of a tag. > One outstanding task is to clean up the javacc doc generation and link that with the doc release as well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-86) Plans for secure socket transports

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-86?page=com.atlassian.jira.plugin... ] Work on TEIIDSB-86 started by Steven Hawkins. --------------------------------------------- > Plans for secure socket transports > ---------------------------------- > > Key: TEIIDSB-86 > URL: https://issues.jboss.org/browse/TEIIDSB-86 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 1.1.0 > > > The Teiid Spring Boot configuration allows for only non-secured pg / JDBC socket transports. For external client scenarios and even for varying degrees of compliance with intra-cluster traffic, a secure layer may be required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5509) Ensure compatibility with vert.x postgresql client

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5509?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5509: ---------------------------------- Fix Version/s: 12.3 (was: 12.2) > Ensure compatibility with vert.x postgresql client > -------------------------------------------------- > > Key: TEIID-5509 > URL: https://issues.jboss.org/browse/TEIID-5509 > Project: Teiid > Issue Type: Task > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.3 > > > Vert.x has support for a async/reactive pg client. We should ensure that works with our pg protocol. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5684) Show Latest Deployed Date of VDB in metadata tables

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5684?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5684. ----------------------------------- Resolution: Done In addition to using the wildfly attribute, I've added loadingTimestamp and activeTimestamp to the virtualdatabases table, which will work for all teiid platforms. > Show Latest Deployed Date of VDB in metadata tables > --------------------------------------------------- > > Key: TEIID-5684 > URL: https://issues.jboss.org/browse/TEIID-5684 > Project: Teiid > Issue Type: Enhancement > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > There is no easy way to tell when a VDB is last deployed on the server without scanning through server.log. This is very useful metadata to have handy. > Is it possible to show when a VDB is last deployed on the server via metadata tables. > May be show this info along with VDB name and version in SYS.VirtualDatabase table? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2019