November 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3798) response code for "primary key of parent table not found"

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3798?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3798: ------------------------------------- Ok, agree. [~prashanthi1] Did you see a empty array as response? Because of you see that, that is also right based on above discussion. If you really care about 404, then you should probably issue a entity call based on its ID first then the relationship call. > response code for "primary key of parent table not found" > --------------------------------------------------------- > > Key: TEIID-3798 > URL: https://issues.jboss.org/browse/TEIID-3798 > Project: Teiid > Issue Type: Bug > Reporter: Prashanthi Kairuppala > Assignee: Steven Hawkins > Priority: Critical > > Hi, > > When the primary key of the parent table is not found in the below kind of odata URL: > > odata/VDB/ParentTable/123/ChildTable > > then the response code is expected to be 404/500 or any error code, but we are getting 200 OK success code. > > Thanks, > Prashanthi. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3798) response code for "primary key of parent table not found"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3798?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3798: --------------------------------------- I'm inclined to leave the current behavior as that matches odata.org. > response code for "primary key of parent table not found" > --------------------------------------------------------- > > Key: TEIID-3798 > URL: https://issues.jboss.org/browse/TEIID-3798 > Project: Teiid > Issue Type: Bug > Reporter: Prashanthi Kairuppala > Assignee: Steven Hawkins > Priority: Critical > > Hi, > > When the primary key of the parent table is not found in the below kind of odata URL: > > odata/VDB/ParentTable/123/ChildTable > > then the response code is expected to be 404/500 or any error code, but we are getting 200 OK success code. > > Thanks, > Prashanthi. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3798) response code for "primary key of parent table not found"

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3798?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3798: ------------------------------------- In Teiid's case, relationship always terminates in a collection, but the quirky thing here is the entity does not exist, that is why I was leaning towards the 404. If entity existed and entity relationship not, then it is empty collection with 200. But in Teiid case, it hard to differentiate between these two with SQL query generated. > response code for "primary key of parent table not found" > --------------------------------------------------------- > > Key: TEIID-3798 > URL: https://issues.jboss.org/browse/TEIID-3798 > Project: Teiid > Issue Type: Bug > Reporter: Prashanthi Kairuppala > Assignee: Steven Hawkins > Priority: Critical > > Hi, > > When the primary key of the parent table is not found in the below kind of odata URL: > > odata/VDB/ParentTable/123/ChildTable > > then the response code is expected to be 404/500 or any error code, but we are getting 200 OK success code. > > Thanks, > Prashanthi. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3798) response code for "primary key of parent table not found"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3798?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3798: --------------------------------------- I should have added that the same behavior is in the V3/V4 RI as well: http://services.odata.org/V4/OData/OData.svc/Categories(-1)/Products >From the requesting related entities section: - If the navigation property does not exist on the entity indicated by the request URL, the service returns 404 Not Found. - If the relationship terminates on a collection, the response MUST be the format-specific representation of the collection of related entities. If no entities are related, the response is the format-specific representation of an empty collection. The 404 behavior is seen with using a bogus entity /NoProducts. Seems ambiguous as to whether that a non-existent parent should return a 404. > response code for "primary key of parent table not found" > --------------------------------------------------------- > > Key: TEIID-3798 > URL: https://issues.jboss.org/browse/TEIID-3798 > Project: Teiid > Issue Type: Bug > Reporter: Prashanthi Kairuppala > Assignee: Steven Hawkins > Priority: Critical > > Hi, > > When the primary key of the parent table is not found in the below kind of odata URL: > > odata/VDB/ParentTable/123/ChildTable > > then the response code is expected to be 404/500 or any error code, but we are getting 200 OK success code. > > Thanks, > Prashanthi. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3798) response code for "primary key of parent table not found"

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3798?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3798: ------------------------------------- I could only find reference in V4 spec http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... IMO, V2 spec mutilated when converted to webpages on odata.org, I could not find the original word documents. In general if the URL resource does not exist, it should be 404 > response code for "primary key of parent table not found" > --------------------------------------------------------- > > Key: TEIID-3798 > URL: https://issues.jboss.org/browse/TEIID-3798 > Project: Teiid > Issue Type: Bug > Reporter: Prashanthi Kairuppala > Assignee: Steven Hawkins > Priority: Critical > > Hi, > > When the primary key of the parent table is not found in the below kind of odata URL: > > odata/VDB/ParentTable/123/ChildTable > > then the response code is expected to be 404/500 or any error code, but we are getting 200 OK success code. > > Thanks, > Prashanthi. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3798) response code for "primary key of parent table not found"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3798?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3798: --------------------------------------- While this does make sense, our current behavior matches that of odata.org: http://services.odata.org/OData/OData.svc/Categories(-1)/Products Can you provide a spec link for the expected error code? > response code for "primary key of parent table not found" > --------------------------------------------------------- > > Key: TEIID-3798 > URL: https://issues.jboss.org/browse/TEIID-3798 > Project: Teiid > Issue Type: Bug > Reporter: Prashanthi Kairuppala > Assignee: Steven Hawkins > Priority: Critical > > Hi, > > When the primary key of the parent table is not found in the below kind of odata URL: > > odata/VDB/ParentTable/123/ChildTable > > then the response code is expected to be 404/500 or any error code, but we are getting 200 OK success code. > > Thanks, > Prashanthi. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3798) response code for "primary key of parent table not found"

by Prashanthi Kairuppala (JIRA)

Prashanthi Kairuppala created TEIID-3798: -------------------------------------------- Summary: response code for "primary key of parent table not found" Key: TEIID-3798 URL: https://issues.jboss.org/browse/TEIID-3798 Project: Teiid Issue Type: Bug Reporter: Prashanthi Kairuppala Assignee: Steven Hawkins Priority: Critical Hi, When the primary key of the parent table is not found in the below kind of odata URL: odata/VDB/ParentTable/123/ChildTable then the response code is expected to be 404/500 or any error code, but we are getting 200 OK success code. Thanks, Prashanthi. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3797) Use the term local consistently

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3797?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3797. ----------------------------------- Resolution: Done Converted the overloaded term embedded to local and updated the docs. > Use the term local consistently > ------------------------------- > > Key: TEIID-3797 > URL: https://issues.jboss.org/browse/TEIID-3797 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > To not have confusion with Teiid embedded, we should use the term local consistently to refer to the in-vm connections. This means updating the docs/config and renaming the embeddedprofile to localprofile. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3520) Extend the Swagger support in the WS Translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3520?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3520: ------------------------------------- You can use the "NameInSource" property for "path" based name, then use the OperationID as the Procedure Name. Use "proc.setNameInSouce(...)" > Extend the Swagger support in the WS Translator > ----------------------------------------------- > > Key: TEIID-3520 > URL: https://issues.jboss.org/browse/TEIID-3520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Kylin Soong > Fix For: 9.0 > > > http://swagger.io is popular REST service description framework, it defines a specification http://swagger.io/specification/ for REST service definition. > Teiid WS translator should add the ability to read this file (like WSDL) and provide the REST methods as endpoints that can be consumed from Teiid. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3520) Extend the Swagger support in the WS Translator

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3520?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3520: ------------------------------------ * '"operationId" needs to be the name of the procedure' operationId is unique for the operation, but it not transparent for the API consumer, so I think the path can only be the procedure name, for example, if has api path '/customer/getByID', then procedure name can be 'customer_getById()' > Extend the Swagger support in the WS Translator > ----------------------------------------------- > > Key: TEIID-3520 > URL: https://issues.jboss.org/browse/TEIID-3520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Kylin Soong > Fix For: 9.0 > > > http://swagger.io is popular REST service description framework, it defines a specification http://swagger.io/specification/ for REST service definition. > Teiid WS translator should add the ability to read this file (like WSDL) and provide the REST methods as endpoints that can be consumed from Teiid. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2015