November 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5537) Move Thorntail examples to use new modules

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5537?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-5537. --------------------------------- Resolution: Done > Move Thorntail examples to use new modules > ------------------------------------------ > > Key: TEIID-5537 > URL: https://issues.jboss.org/browse/TEIID-5537 > Project: Teiid > Issue Type: Sub-task > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 11.2.1 > > > Also, how about closing the "thorntail-examples" repo and merging the examples with the new Thontail repo? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

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

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5545: ------------------------------------- Applied the issue upstream, we can wait till 4.6 release or bring in a forked Teiid branch? > 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.0 > > > 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)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5547) Issues with REST produces property

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5547?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5547. ----------------------------------- Resolution: Done Updated to replace all non word characters with _, and updated the docs. There's still no upfront validation that the text entered is valid mime type. > Issues with REST produces property > ---------------------------------- > > Key: TEIID-5547 > URL: https://issues.jboss.org/browse/TEIID-5547 > Project: Teiid > Issue Type: Bug > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 11.2.1 > > > The handling of PRODUCES for values other than xml, plain, and json may fail - such as using a comma separated list, */*, etc. as the generated method name may contain invalid characters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5547) Issues with REST produces property

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5547?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5547: ---------------------------------- Description: The handling of PRODUCES for values other than xml, plain, and json may fail - such as using a comma separated list, */*, etc. as the generated method name may contain invalid characters. (was: The handling of PRODUCES "any" and the documentation for values other than plain, xml, and json needs corrected.) > Issues with REST produces property > ---------------------------------- > > Key: TEIID-5547 > URL: https://issues.jboss.org/browse/TEIID-5547 > Project: Teiid > Issue Type: Bug > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 11.2.1 > > > The handling of PRODUCES for values other than xml, plain, and json may fail - such as using a comma separated list, */*, etc. as the generated method name may contain invalid characters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5544) Comments in source model lead to vdb with erroneous annotation (Term attribute is missing)

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5544?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5544. ----------------------------------- Fix Version/s: 11.0.3 11.1.2 11.2.1 Resolution: Done Updated the alias to Core and added the Core schema. > Comments in source model lead to vdb with erroneous annotation (Term attribute is missing) > ------------------------------------------------------------------------------------------ > > Key: TEIID-5544 > URL: https://issues.jboss.org/browse/TEIID-5544 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.0.3, 11.1.2, 12.0, 11.2.1 > > > A detailed description of the issue with an example of a wrongly generated metadata.xml can be found under the following link > https://github.com/SAP/openui5/issues/2288 > In short: When a comment is added to an attribute in the source model, the generated annotation for the comment has the "Term" attribute missing. The Sapui5/ OpenUI5 library crashes when trying to parse the file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5547) Issues with REST produces property

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5547: ------------------------------------- Summary: Issues with REST produces property Key: TEIID-5547 URL: https://issues.jboss.org/browse/TEIID-5547 Project: Teiid Issue Type: Bug Components: Server Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.0, 11.2.1 The handling of PRODUCES "any" and the documentation for values other than plain, xml, and json needs corrected. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5546) Namespace resolution on vdb level

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5546?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5546: ---------------------------------- Fix Version/s: 12.0 11.2.1 > Namespace resolution on vdb level > --------------------------------- > > Key: TEIID-5546 > URL: https://issues.jboss.org/browse/TEIID-5546 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 10.3.5 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Priority: Major > Labels: ddl, namespace, rest, teiid > Fix For: 12.0, 11.2.1 > > > This does work in a DDL based vdb: > {code:sql} > create database vdb version '1.2.0' OPTIONS ("{http://teiid.org/rest}auto-generate" 'true'); > {code} > This doesn't: > {code:sql} > create database vdb version '1.2.0' OPTIONS ("teiid_rest:auto-generate" 'true'); > {code} > It would be nice if the namespace resolution also worked at vdb level. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5546) Namespace resolution on vdb level

by Bram Gadeyne (Jira)

Bram Gadeyne created TEIID-5546: ----------------------------------- Summary: Namespace resolution on vdb level Key: TEIID-5546 URL: https://issues.jboss.org/browse/TEIID-5546 Project: Teiid Issue Type: Feature Request Affects Versions: 10.3.5 Reporter: Bram Gadeyne Assignee: Steven Hawkins This does work in a DDL based vdb: {code:sql} create database vdb version '1.2.0' OPTIONS ("{http://teiid.org/rest}auto-generate" 'true'); {code} This doesn't: {code:sql} create database vdb version '1.2.0' OPTIONS ("teiid_rest:auto-generate" 'true'); {code} It would be nice if the namespace resolution also worked at vdb level. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5425) Concurrency/timing issues observed with travis builds

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5425?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5425: ---------------------------------- Fix Version/s: 12.x > Concurrency/timing issues observed with travis builds > ----------------------------------------------------- > > Key: TEIID-5425 > URL: https://issues.jboss.org/browse/TEIID-5425 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.x > > > Several unit tests have been observed to fail during travis builds occasionally: > 1. TestODBCSocketTransport.testRegClass:757 Â» PSQL ResultSet not positioned prope... > 2. TestExternalMatViews.testLazyUpdate:930 expected:<2> but was:<1> (see https://api.travis-ci.org/v3/job/405801976/log.txt) > 3. [ERROR] TestLocalConnections.testWaitForLoadTimeout:475 > 4. From https://api.travis-ci.org/v3/job/415138409/log.txt > [ERROR] testReplication(org.teiid.systemmodel.TestReplication) Time elapsed: 35.21 s <<< FAILURE! > java.lang.AssertionError: expected:<0.9164140964242746> but was:<0.18750528722359294> > at org.teiid.systemmodel.TestReplication.testReplication(TestReplication.java:122) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[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 reassigned TEIID-5545: ------------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) Assigning to Ramesh to get the upstream issue into a release. > 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.0 > > > 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)

5 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2018