November 2018 - 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 Christoph John (Jira)

Christoph John created TEIID-5545: ------------------------------------- Summary: 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: Steven Hawkins 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5543) Configuration Option for default OData format

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5543?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-5543: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Configuration Option for default OData format > ---------------------------------------------- > > Key: TEIID-5543 > URL: https://issues.jboss.org/browse/TEIID-5543 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Optional > > It would be great to have a config option to set the default format for odata responses which is chosen if no Accept header was set to request the format. > SapUI5 / OpenUI5 for example sends Accept * / * > Would be great if the admin could decide on the default format in such cases. > See related discussion https://developer.jboss.org/thread/279113 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

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

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5544?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5544: ------------------------------------- This should be fixed for 11.x > 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: Ramesh Reddy > Priority: Major > Fix For: 12.0 > > > 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5541) Incorrect parsing of xml with XmlTable

by dalex dalex (Jira)

[ https://issues.jboss.org/browse/TEIID-5541?page=com.atlassian.jira.plugin... ] dalex dalex commented on TEIID-5541: ------------------------------------ Hi [~shawkins], I've checked new changes and now everything works as expected. Thx for the quick fix. > Incorrect parsing of xml with XmlTable > -------------------------------------- > > Key: TEIID-5541 > URL: https://issues.jboss.org/browse/TEIID-5541 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 11.1 > Environment: teiid-11.1.0 (from 01.09.2018) on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 11.0.3, 11.1.2, 12.0, 11.2.1 > > > Running the query: > {code:sql} > Begin > Declare xml xcontent = '<root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <report> > <data> > <year xsi:type="decimal">2018</year> > </data> > </report> > <waitSeconds xsi:type="decimal">13</waitSeconds> > </root>' ; > Select * > From > XmlTable( > XmlNamespaces ('http://www.w3.org/2001/XMLSchema-instance' as xsi), > '/root/report/data' > PASSING xcontent > Columns > "year" integer, > waitSeconds xml Path 'root()/root/waitSeconds', > waitSecondsStr string Path 'root()/root/waitSeconds' > )a ; > End ;; > {code} > and having a look at the structure we can see that the value 13 should be returned, while the value is not picked from xml for result. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5536) Create separate repository for Thorntail modules

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5536?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5536: --------------------------------------- After the pull request with various changes: - 1.0.1 release (in progress). For some reason I need credentials for server ossrh even though that is not called that in our distributionManagement. Perhaps that's coming in from the parent somehow. - deployment of the examples is dia - a snapshot ci build has been added https://travis-ci.org/teiid/teiid-thorntail the logs needed trimming as the output exceed the default limits. There are a lot of "error" messages similar to Could not find artifact org.apache.cxf:cxf-rt-databinding-aegis:jar:3.1.12 that needed suppressed - THORN-791. The initial run took 15 minutes though... TODO: - expand the readme, add a build badge, etc. - tests either in the main project or based upon the examples - a full release triggered off of the creation of a label > Create separate repository for Thorntail modules > ------------------------------------------------ > > Key: TEIID-5536 > URL: https://issues.jboss.org/browse/TEIID-5536 > Project: Teiid > Issue Type: Task > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > > THORN-2232 Removes the Teiid modules from the core Thorntail repo for better release management. However, Teiid Thorntail would need a new home. > Most notable breaking change will be, the package names will change from that of Thorntail. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

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

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5537?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5537: --------------------------------------- A follow on to this is to document somewhere the old to new module name mapping. > 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 > > 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)

6 years, 1 month

1
0
0 / 0

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

by Ted Jones (Jira)

[ https://issues.jboss.org/browse/TEIID-5544?page=com.atlassian.jira.plugin... ] Ted Jones commented on TEIID-5544: ---------------------------------- Looks like we are not handing annotations correctly. See: https://stackoverflow.com/questions/42105353/olingo-v4-annotations-not-ge... > 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: Ramesh Reddy > Priority: Major > Fix For: 12.0 > > > 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)

6 years, 1 month

1
0
0 / 0

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

by Ted Jones (Jira)

[ https://issues.jboss.org/browse/TEIID-5544?page=com.atlassian.jira.plugin... ] Ted Jones reassigned TEIID-5544: -------------------------------- Assignee: Ramesh Reddy > 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: Ramesh Reddy > Priority: Major > Fix For: 12.0 > > > 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5541) Incorrect parsing of xml with XmlTable

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5541?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5541: --------------------------------------- > At least it breaks previous behavior. Yes, that is another related case that needs addressed - we can use projection without streaming, but we can't do streaming processing without projection. This case wouldn't have been triggered before except in the case of a column path having multiple context items, which unfortunately there wasn't a test for. There's a new commit to correct this. > Incorrect parsing of xml with XmlTable > -------------------------------------- > > Key: TEIID-5541 > URL: https://issues.jboss.org/browse/TEIID-5541 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 11.1 > Environment: teiid-11.1.0 (from 01.09.2018) on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 11.0.3, 11.1.2, 12.0, 11.2.1 > > > Running the query: > {code:sql} > Begin > Declare xml xcontent = '<root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <report> > <data> > <year xsi:type="decimal">2018</year> > </data> > </report> > <waitSeconds xsi:type="decimal">13</waitSeconds> > </root>' ; > Select * > From > XmlTable( > XmlNamespaces ('http://www.w3.org/2001/XMLSchema-instance' as xsi), > '/root/report/data' > PASSING xcontent > Columns > "year" integer, > waitSeconds xml Path 'root()/root/waitSeconds', > waitSecondsStr string Path 'root()/root/waitSeconds' > )a ; > End ;; > {code} > and having a look at the structure we can see that the value 13 should be returned, while the value is not picked from xml for result. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5541) Incorrect parsing of xml with XmlTable

by dalex dalex (Jira)

[ https://issues.jboss.org/browse/TEIID-5541?page=com.atlassian.jira.plugin... ] dalex dalex commented on TEIID-5541: ------------------------------------ [~shawkins] do you mean by the phrase "So for now document projection will not be allowed when root() is used." that now such query: {code:sql} Begin Declare xml x = '<root><def><test1>10</test1><test1>20</test1></def><abc>22</abc></root>'; Select * From XmlTable ( '/root/abc' Passing x Columns a string Path '.' ,b string Path 'root()' )xx; End;; {code} will return empty values for a and b though before your changes it returned 22 for a and 102022 for b. I'm afraid that it's incorrect solution. At least it breaks previous behavior. > Incorrect parsing of xml with XmlTable > -------------------------------------- > > Key: TEIID-5541 > URL: https://issues.jboss.org/browse/TEIID-5541 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 11.1 > Environment: teiid-11.1.0 (from 01.09.2018) on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 11.0.3, 11.1.2, 12.0, 11.2.1 > > > Running the query: > {code:sql} > Begin > Declare xml xcontent = '<root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <report> > <data> > <year xsi:type="decimal">2018</year> > </data> > </report> > <waitSeconds xsi:type="decimal">13</waitSeconds> > </root>' ; > Select * > From > XmlTable( > XmlNamespaces ('http://www.w3.org/2001/XMLSchema-instance' as xsi), > '/root/report/data' > PASSING xcontent > Columns > "year" integer, > waitSeconds xml Path 'root()/root/waitSeconds', > waitSecondsStr string Path 'root()/root/waitSeconds' > )a ; > End ;; > {code} > and having a look at the structure we can see that the value 13 should be returned, while the value is not picked from xml for result. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2018