Joe Rattazzi created OLINGO-1630:
------------------------------------
Summary: Olingo does not support server-side Key-As-Segment
Key: OLINGO-1630
URL: https://issues.apache.org/jira/browse/OLINGO-1630
Project: Olingo
Issue Type: Bug
Reporter: Joe Rattazzi
h2. *What's wrong*
Introduced in OData v4.01, OData supports "Key as Segment":
[https://www.odata.org/blog/OData-401-Committee-Spec-Published/]
{quote}Key as Segment – Common semantics for representing keys within a URL as
a segment, rather than enclosed in parenthesis.{quote}
It appears to work fine from the client-side, but the server-side
implementation is missing.
*Link to specification:*
[https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#_Toc31360937]
Example
* OData v4.0: [http://host/service/Employees('A1245')]
* OData v4.01 with Key-As-Segment: http://host/service/Employees/A1245
h2. Current User experience:
UriParserException
h2. Proposed Change
Add the support for key-as-segment in {*}ResourcePathParser{*}.
Additionally, add support for users to opt in to the new functionality as part
of the EntitySet definition, in case this is a breaking change for some use
cases. Create a boolean such as {*}keyAsSegmentAllowed{*}, defaulting to
{*}false{*}.
*Notes*
We have a change to contribute, pending approval as a valid issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
