[
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)