You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Ramya Vasanth (Jira)" <ji...@apache.org> on 2020/10/29 07:04:00 UTC

[jira] [Created] (OLINGO-1489) ODataV4: Support custom aggregates that have the same name a property

Ramya Vasanth created OLINGO-1489:
-------------------------------------

             Summary: ODataV4: Support custom aggregates that have the same name a property
                 Key: OLINGO-1489
                 URL: https://issues.apache.org/jira/browse/OLINGO-1489
             Project: Olingo
          Issue Type: New Feature
    Affects Versions: (Java) V4 4.7.1
            Reporter: Ramya Vasanth


According to the specification

[http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/csprd03/odata-data-aggregation-ext-v4.0-csprd03.html#_Toc426533698] :

 

_If the custom aggregate is associated with a structured type, the value of the_ _Qualifier_ _attribute MAY be identical to the name of a declared property of the structured type. In this case, the value of the annotation MUST have the same value as the_ _Type_ _attribute of the declared property. This is typically done when the custom aggregate is used as a default aggregate for that property. In this case, the name refers to the custom aggregate within an aggregate expression without a_ _[with|http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/csprd03/odata-data-aggregation-ext-v4.0-csprd03.html#_Toc361047145]_ _clause, and to the property in all other cases._

Url's of the form 

GET Sales?$apply=aggregate(amount)

 and

GET Sales?$apply=aggregate(amount with sum as amount)

should work.

However, it is rejected by Olingo



--
This message was sent by Atlassian Jira
(v8.3.4#803005)