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] Updated: (ODATA-581) Remove parameterless aggregate() transformation

     [ http://tools.oasis-open.org/issues/browse/ODATA-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-581:



> Remove parameterless aggregate() transformation
> -----------------------------------------------
>                 Key: ODATA-581
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-581
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Extension for Data Aggregation 
>    Affects Versions: V4.0_CSD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_CSD02
> the groupiby transformation splits the input set into subsets based on the specified grouping properties, applies the specified transformation to each set, and then combines them into a single result.
> In some cases it is useful to do grouping without any transformation of the intermediate subsets in order to get the unique combination of values across the grouping properties. In CSD01 we allowed specification of the aggregate transformation with no parameters as a way to say "apply grouping without any aggregate".  so Customers?$apply=groupby((Name),aggregate()) would return the distinct customer names without applying an aggregate.
> Later, we added an overload of the groupby method that took only the grouping properties, not the parameterless aggregate method, and said that the two were equivalent.  So the same request could be (more simply and intuitively) Customers?$apply=groupby((Name)).
> However, we didn't get rid of the old syntax, we just defined the new syntax as a shortcut for passing the paramterless aggregate as a second argument. Which means we have two ways of doing the same thing, one short and intuitive, and one through what looks like a bit of a hack.
> We have no other reason to keep the parameterless aggregate, so we should go back to requiring that aggregate have one or more parameters.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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