[OASIS Issue Tracker] (ODATA-1395) Clarify impact of applying expand to subsequent transformations

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Gerald Krause created ODATA-1395:
------------------------------------

             Summary: Clarify impact of applying expand to subsequent transformations 
                 Key: ODATA-1395
                 URL: https://issues.oasis-open.org/browse/ODATA-1395
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: Data Aggregation
    Affects Versions: V4.0_CSD03
         Environment: Proposed
            Reporter: Gerald Krause
             Fix For: V4.0_CSD04


Property paths used in a {{$apply}} transformation by default may refer to any instances that can be directly or indirectly reached via navigation properties. They are all part of the input set of the transformation.


 The preceding {{expand}} transformation limits the input set to those navigation paths constructed from the navigation property given as first argument to {{expand}}, possibly nested several times, reaching target instances that match the given filter expression.


 From the current text this limitation does not become clear.


 Furthermore, {{groupby}} may follow an expand transformation. The definition of {{groupby}} currently refers to an âinitialâ set, and it should be clarified that this is actually the input set, e.g. the result of the preceding {{expand}}.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)