[OASIS Issue Tracker] (ODATA-1556) Entities with ambiguous property values

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Heiko Theissen created ODATA-1556:
-------------------------------------

             Summary: Entities with ambiguous property values
                 Key: ODATA-1556
                 URL: https://issues.oasis-open.org/browse/ODATA-1556
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: Data Aggregation
            Reporter: Heiko Theissen


The output set of a transformation has a context URL of the form [Collection of Entities|https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_CollectionofEntities], but it can contain the same entity multiple times, even with conflicting properties:
{code}
GET /service/Products?$apply=
  concat(compute(0.1 as Discount),
         compute(0.2 as Discount))
{code}
The OData-Aggr specification is not always prepared for such situations.

h2. groupby
What does grouping by such an ambiguous entity mean? What is the {{Discount}} in the response to the following request?
{code}
GET /service/Sales?$apply=
  concat(transformnested(Product,compute(0.1 as Discount)),
         transformnested(Product,compute(0.2 as Discount)))
  /groupby((Product))
  &$expand=Product($select=Discount)
{code}

h2. aggregate
Aggregation considers only distinct entities, but which {{Discount}} is used in the following request?
{code}
GET /service/Sales?$apply=
  concat(transformnested(Product,compute(0.1 as Discount)),
         transformnested(Product,compute(0.2 as Discount)))
  /aggregate(Product/Discount with max as MaxDiscount)
{code}



--
This message was sent by Atlassian Jira
(v8.3.3#803004)