[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1444) groupby algorithm does not cover "select distinct" case
Heiko Theissen created ODATA-1444: ------------------------------------- Summary: groupby algorithm does not cover "select distinct" case Key: ODATA-1444 URL: https://issues.oasis-open.org/browse/ODATA-1444 Project: OASIS Open Data Protocol (OData) TC Issue Type: Improvement Components: Data Aggregation Affects Versions: V4.0_CS02 Reporter: Heiko Theissen Fix For: V4.0_CSD04 The four-step algorithm given at the beginning of the groupby transformation does not describe what happens for {{Products?$apply=groupby((Category))}}. According to a later remark, this is supposed to select only the distinct {{Categories}}. But, after step 1, I have two subsets ||ID||Category||Name||Color||TaxRate|| |P1|PG1|Sugar|White|0.06| |P2|PG1|Coffee|Brown|0.06| and ||ID||Category||Name||Color||TaxRate|| |P3|PG2|Paper|White|0.14| |P4|PG2|Pencil|Black|0.14| Step 2 cannot be carried out due to lack of a second parameter. Step 3 has no effect. Step 4 concatenates these two subsets again, so that the overall effect is of {{groupby((Category),identity)}}. To keep the case without second parameter within the four-step framework, step 2 must essentially produce an instance without properties, leading to subsets ||ID||Category||Name||Color||TaxRate|| |Â|Â|Â|Â| | and ||ID||Category||Name||Color||TaxRate|| |Â|Â|Â|Â| | which step 3 would then change to ||ID||Category||Name||Color||TaxRate|| |Â|PG1|Â|Â| | and ||ID||Category||Name||Color||TaxRate|| |Â|PG2|Â|Â| | -- This message was sent by Atlassian Jira (v8.3.3#803004)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]