June 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4007) Unparseable model name if user changes odata4 context root

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4007?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4007: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1313626|https://bugzilla.redhat.com/show_bug.cgi?id=1313626] from ON_QA to VERIFIED > Unparseable model name if user changes odata4 context root > ---------------------------------------------------------- > > Key: TEIID-4007 > URL: https://issues.jboss.org/browse/TEIID-4007 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.x > Reporter: Juraj Duráni > Assignee: Juraj Duráni > Fix For: 9.0, 8.12.5, 8.13.2 > > > If user changes root context of odata4 service, Teiid does not parse model name from the URI and throws TEIID16022 instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3906) OData v4 - definition of OData-Isolation header is either being ignored or is not implemented correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3906?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3906: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1298916|https://bugzilla.redhat.com/show_bug.cgi?id=1298916] from ON_QA to VERIFIED > OData v4 - definition of OData-Isolation header is either being ignored or is not implemented correctly > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-3906 > URL: https://issues.jboss.org/browse/TEIID-3906 > Project: Teiid > Issue Type: Sub-task > Components: OData > Affects Versions: 8.12.3 > Environment: Teiid - OData v4 > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > Teiid does not process header *OData-Isolation: snapshot* defined in request correctly. > * if service (Teiid) does not support this option it must return error 412 > * if Teiid does supports this option then it is not processed correctly, because modifications made during request are visbile > See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4035) Parameter alias without value returns http status code 500

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4035?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4035: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1316466|https://bugzilla.redhat.com/show_bug.cgi?id=1316466] from ON_QA to VERIFIED > Parameter alias without value returns http status code 500 > ---------------------------------------------------------- > > Key: TEIID-4035 > URL: https://issues.jboss.org/browse/TEIID-4035 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > *URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView/?$filter... > *Result:* OData Library: An exception without message text was thrown. > See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4044) OData ignores entities with empty list of related entities if $filter is applied to expanded entities

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4044?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4044: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1316476|https://bugzilla.redhat.com/show_bug.cgi?id=1316476] from ON_QA to VERIFIED > OData ignores entities with empty list of related entities if $filter is applied to expanded entities > ----------------------------------------------------------------------------------------------------- > > Key: TEIID-4044 > URL: https://issues.jboss.org/browse/TEIID-4044 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > If user want to apply filter for related entities, OData service should return all entities, not only those with non-empty collection of related entities. > *Example:* > *URL:* http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Order... > *Result:* OData returns only 2 customers (both have at least one order with place "town") > *Expectation:* OData should return all 4 customers (two of them should have empty list of orders) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4047) OData - $top with negative value return status code 500

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4047?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4047: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1316484|https://bugzilla.redhat.com/show_bug.cgi?id=1316484] from ON_QA to VERIFIED > OData - $top with negative value return status code 500 > ------------------------------------------------------- > > Key: TEIID-4047 > URL: https://issues.jboss.org/browse/TEIID-4047 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > OData request with query option $top with negative value returns status code 500. The root cause is SQLException. OData service should check passed value and return e.g. 400 instead. > *URL:* http://localhost:8080/odata4/olingo_basic/Source/Customers/?$top=-1 > See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4054) OData - creation of entity (POST) returns exception (status code 500)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4054?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4054: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1316490|https://bugzilla.redhat.com/show_bug.cgi?id=1316490] from ON_QA to VERIFIED > OData - creation of entity (POST) returns exception (status code 500) > --------------------------------------------------------------------- > > Key: TEIID-4054 > URL: https://issues.jboss.org/browse/TEIID-4054 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Labels: alpha3 > Fix For: 9.0, 8.12.5 > > > Creation of entity returns exception \[1\]. Representation of entity \[2\]. Http request \[3\]. Header \[4\]. Same exception with of JSON format. > \[1\] > {code:plain} > TEIID10076 Invalid conversion from type class java.lang.Object with value 'java.util.GregorianCalendar[time=4000,areFieldsSet=true,areAllFieldsSet=true, > lenient=true,zone=sun.util.calendar.ZoneInfo[id="GMT",offset=0,dstSavings=0,useDaylight=false,transitions=0,lastRule=null],f > irstDayOfWeek=2,minimalDaysInFirstWeek=4,ERA=1,YEAR=1970,MONTH=0,WEEK_OF_YEAR=1, > WEEK_OF_MONTH=1,DAY_OF_MONTH=1,DAY_OF_YEAR=1,DAY_OF_WEEK=5,DAY_OF_WEEK_IN_MONTH=1, > AM_PM=0,HOUR=0,HOUR_OF_DAY=0,MINUTE=0,SECOND=4,MILLISECOND=0,ZONE_OFFSET=0,DST_OFFSET=0]' > to type class java.sql.Time > {code} > \[2\] > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <entry xmlns="http://www.w3.org/2005/Atom" xmlns:d="http://docs.oasis-open.org/odata/ns/data" xmlns:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml" xmlns:m="http://docs.oasis-open.org/odata/ns/metadata"> > <category scheme="http://docs.oasis-open.org/odata/ns/scheme" /> > <content type="application/xml"> > <m:properties> > <d:intkey m:type="Int32">4</d:intkey> > <d:intnum m:type="Int32">4</d:intnum> > <d:stringkey>4</d:stringkey> > <d:stringval>value_4</d:stringval> > <d:booleanval m:type="Boolean">false</d:booleanval> > <d:decimalval m:type="Double">-20.4</d:decimalval> > <d:timeval m:type="TimeOfDay">00:00:04</d:timeval> > <d:dateval m:type="Date">2004-04-04</d:dateval> > <d:timestampval m:type="DateTimeOffset">2004-01-01T00:00:04Z</d:timestampval> > <d:clobval m:type="Binary">Y2xvYl92YWx1ZV8wMDAwNA==</d:clobval> > </m:properties> > </content> > </entry> > {code} > \[3\] > POST http://localhost:8080/odata4/olingo_basic/Source/PostTable(4) > \[4\] > Content-type: application/xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4055) OData - updating of raw value fails (PUT method to URL with path $value)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4055?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4055: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1316494|https://bugzilla.redhat.com/show_bug.cgi?id=1316494] from ON_QA to VERIFIED > OData - updating of raw value fails (PUT method to URL with path $value) > ------------------------------------------------------------------------ > > Key: TEIID-4055 > URL: https://issues.jboss.org/browse/TEIID-4055 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 9.0, 8.12.5 > > > *URL:* http://localhost:8080/odata4/olingo_basic/Source/PutPropTable(1)/name/$value > *Method:* PUT > *Header:* Content-type: text/plain > *Body of request:* it is build like this: > {code:java} > new ByteArrayInputStream("6".getBytes()) > {code} > *Response:* The content-type range 'application/xml' is not supported as value of the Accept header. > *Status code:* 406 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4064) OData - missing non-nullable property

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4064?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4064: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1316511|https://bugzilla.redhat.com/show_bug.cgi?id=1316511] from ON_QA to VERIFIED > OData - missing non-nullable property > ------------------------------------- > > Key: TEIID-4064 > URL: https://issues.jboss.org/browse/TEIID-4064 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.0, 8.12.5 > > > Change DDL for tables Customer and Orders in VDB as follows: > {code:sql} > CREATE FOREIGN TABLE Customers ( > id integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'), > name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.CUSTOMERS'); > CREATE FOREIGN TABLE Orders ( > id integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'), > customerid integer, > place varchar(10), > FOREIGN KEY (customerid) REFERENCES Customers(id)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.ORDERS'); > {code} > Note, that both tables have same name of primary key named "id". > Invoke GET method to URL http://localhost:8080/odata4/olingo_basic/Source/Customers/?$count=true&$... > *Result:* > {code:xml} > <error> > <code>400</code> > <message>The non-nullable property 'id' is missing.</message> > </error> > {code} > Here are selected part of Teiid's log: > *Query:* > {code:sql} > SELECT g10.id, g10.name, g11.id, g11.customerid, g11.place FROM Source.Customers AS g10 LEFT OUTER JOIN Source.Orders AS g11 ON g10.id = g11.customerid ORDER BY g10.id > {code} > *Result:* > |id|name|id|customerid|place| > |1|customer1|1|1|town| > |1|customer1|2|1|state| > |1|customer1|3|1|country| > |1|customer1|4|1|abroad| > |2|customer2|5|2|state| > |2|customer2|6|2|country| > |3|customer3|7|3|town| > |3|customer3|8|3|town| > |4|customer4|<null>|<null>|<null>| -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4057) OData - if PUT fails, next update request fails because table in DB is still locked

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4057?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4057: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1316498|https://bugzilla.redhat.com/show_bug.cgi?id=1316498] from ON_QA to VERIFIED > OData - if PUT fails, next update request fails because table in DB is still locked > ----------------------------------------------------------------------------------- > > Key: TEIID-4057 > URL: https://issues.jboss.org/browse/TEIID-4057 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > I can see (from the log) that processing of PUT request is as follows: > # select record from table > # delete record > # parse entity from HTTP request > # insert new record > But if e.g. step 3 fails, Teiid cancels transaction and returns error. In my opinion, parsing of the entity should be the first step (or at least right after select). > What happen here is, that DELETE statement creates transaction and locks the table. But the transaction is not canceled immediately after cancel request \[1\]. This causes that no other query can succeed, because of lock on the table (EAP uses connection pool and does not close connections immediately and therefore open connection has still one transaction in active state). > *Note:* We use H2 database for testing purpose. But I think that this could happen with any DB. Anyway, parsing of the entity should not be performed after delete. > \[1\] > {code:plain} > 09:35:33,937 DEBUG [org.teiid.TRANSPORT] (New I/O worker #1) Channel closed > 09:40:31,430 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffff7f000001:113c3cbe:56e131a7:e in state RUN > 09:40:31,438 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffff7f000001:113c3cbe:56e131a7:e > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4056) OData - PUT cannot parse entity

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4056?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4056: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1316497|https://bugzilla.redhat.com/show_bug.cgi?id=1316497] from ON_QA to VERIFIED > OData - PUT cannot parse entity > ------------------------------- > > Key: TEIID-4056 > URL: https://issues.jboss.org/browse/TEIID-4056 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > If user want to update entity using HTTP PUT method, OData service returns error that JSON document is not valid. Even if entity is in XML format. > *URL:* http://localhost:8080/odata4/olingo_basic/Source/PutTable(1) or http://localhost:8080/odata4/olingo_basic/Source/PutTable(2) > *Method:* PUT > *Request reader:* Content-type: application/json or Content-type: application/xml > *Error:* The syntax of the JSON document is not valid. > *Entity JSON:* > {code:plain} > {"intnum(a)odata.type":"Int32","intnum":5,"stringval(a)odata.type":"String","stringval":"5","timestampval(a)odata.type":"DateTimeOffset","timestampval":"2005-01-01T00:00:05Z","clobval(a)odata.type":"Binary","clobval":"Y2xvYl92YWx1ZV8wMDAwNQ=="} > {code} > *Entity XML:* > {code:xml} > <?xml version='1.0' encoding='UTF-8'?><entry xmlns="http://www.w3.org/2005/Atom" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:m="http://docs.oasis-open.org/odata/ns/metadata" xmlns:d="http://docs.oasis-open.org/odata/ns/data" xmlns:gml="http://www.opengis.net/gml" xmlns:georss="http://www.georss.org/georss"><category scheme="http://docs.oasis-open.org/odata/ns/scheme"/><content type="application/xml"><m:properties><d:intnum m:type="Int32">4</d:intnum><d:stringval>4</d:stringval><d:timestampval m:type="DateTimeOffset">2004-01-01T00:00:04Z</d:timestampval><d:clobval m:type="Binary">Y2xvYl92YWx1ZV8wMDAwNA==</d:clobval></m:properties></content></entry> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 June 2016