OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (ODATA-1375) Clarify location of custom aggregates in $apply results

Gerald Krause created ODATA-1375:

             Summary: Clarify location of custom aggregates in $apply results
                 Key: ODATA-1375
                 URL: https://issues.oasis-open.org/browse/ODATA-1375
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: Data Aggregation
    Affects Versions: V4.0_CS02
         Environment: Proposed
            Reporter: Gerald Krause
             Fix For: V4.0_CSD04

This problem occurs twice:


The current text in [7.3 Custom Aggregates|http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs02/odata-data-aggregation-ext-v4.0-cs02.html#_Toc435016611] states that the dynamic property with the result of a custom aggregate âMUST always be in the same set as the original property.â

Example 61 following this statement puts the result of the custom aggregate Forecast into the nested Sales structure although the request uses a path expression:

{{GET ~/Products?$apply=groupby((Name), ... Sales/Forecast))}}


The same statement appears in section [7.4 Aliasing|http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs02/odata-data-aggregation-ext-v4.0-cs02.html#_Toc435016612]. Here, it is not wrong, but may draw wrong conclusions , if it is applied to a variation of the request in example 64:

{{GET ~/Products?$apply=groupby((Name),aggregate(Sales/Amount with sum as Total))}}

Then, {{Total}} MUST be placed at the top result level.

This message was sent by Atlassian Jira

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]