You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/05/20 12:09:05 UTC

[jira] [Commented] (SYNCOPE-1086) Avoid to read whole entities to check ETag

    [ https://issues.apache.org/jira/browse/SYNCOPE-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018419#comment-16018419 ] 

ASF subversion and git services commented on SYNCOPE-1086:
----------------------------------------------------------

Commit 9b7abc1804ec2dc21084528333f24489f441d12c in syncope's branch refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=9b7abc1 ]

[SYNCOPE-1086] Providing specific method to fetch only creationDate / lastChangeDate in order to build ETag


> Avoid to read whole entities to check ETag
> ------------------------------------------
>
>                 Key: SYNCOPE-1086
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1086
>             Project: Syncope
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.2.10, 2.0.3
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: 1.2.11, 2.0.4, 2.1.0
>
>
> Currently, in order to check ETag to provide simple locking for concurrent updates via REST, the whole entities (users / groups / any objects) are read.
> This involves internal fetch of a whole set of unused data, some of them (virtual attributes, dynamic memberships) being particularly onerous.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)