-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: V4.0_CSD04
-
Component/s: Data Aggregation
-
Labels:None
-
Environment:
Applied
-
Proposal:
-
Resolution:
The output set of a transformation has a context URL of the form Collection of Entities, but it can contain the same entity multiple times, even with conflicting properties:
GET /service/Products?$apply=
concat(compute(0.1 as Discount),
compute(0.2 as Discount))
The OData-Aggr specification is not always prepared for such situations.
groupby
What does grouping by such an ambiguous entity mean? How many items does the response to the following request contain?
GET /service/Sales?$apply=
concat(transformnested(Product,compute(0.1 as Discount)),
transformnested(Product,compute(0.2 as Discount)))
/groupby((Product/Discount))
What is the Discount in the response to the following request?
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)
aggregate
Aggregation considers only distinct entities, but which Discount is used in the following request?
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)