[OASIS Issue Tracker] Updated: (ODATA-452) Services should be allowed to filter changes based on selected fields

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

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

Michael Pizzo updated ODATA-452:
--------------------------------

    Proposal: 
Services may filter changes based on selected properties, returning only those rows that have changes to the selected fields. Clients must not attempt to compose $select to the delta link.

Client should not be allowed to append any query options to delta links. We have a preference for max page size, so $top/$skip is not needed (and is potentially dangerous based on ordering). Other ways to do $format.

  was:Services may filter changes based on selected properties, returning only those rows that have changes to the selected fields. Clients must not attempt to compose $select to the delta link.


> Services should be allowed to filter changes based on selected fields
> ---------------------------------------------------------------------
>
>                 Key: ODATA-452
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-452
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol 
>    Affects Versions: V4.0_CSD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_CSD02
>
>
> Currently, users are allowed to specify $select in a query for which they track changes, but the $select must not be used to determine whether or not a change matches. That is, the service must return a change to the record even if it doesn't match one of the selected fields. Also, we allow the client to specify a $select on the delta link to request back a different set of fields than on the initial query.
> While many services will not be able to filter based on the set of selected fields (at least until they do change tracking on filtered results), we should allow those that do to be able to do so. Not filtering based on selected fields simply results in over-notification, so this doesn't break anything, but if a client is expecting to get changes for non-selected fields and does not then it would be a data loss.

-- 
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