[
https://issues.apache.org/jira/browse/SYNCOPE-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17560900#comment-17560900
]
ASF subversion and git services commented on SYNCOPE-1687:
----------------------------------------------------------
Commit e962bd0956d013cda6419f8ce1063c653ba55100 in syncope's branch
refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=e962bd0956 ]
[SYNCOPE-1687] Adding prefetch option to PropagationPolicy
> Allow to configure External Resources not to pre-fetch objects during
> propagation
> ---------------------------------------------------------------------------------
>
> Key: SYNCOPE-1687
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1687
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Fix For: 3.0.0
>
>
> The current behavior implemented for propagation task execution is to attempt
> to read upfront the object being propagated.
> This is mainly done with purpose of:
> * translating {{CREATE}} into {{UPDATE}} in case the object is already found
> remotely, and viceversa
> * avoiding to issue {{DELETE}} operation if object is not found
> * avoiding to propagate in case the remote object is found equal to the data
> being propagated
> There are however conditions under which such checks can be seen as an
> overhead rather than an optimization: it makes sense then to let such
> behavior to be configurable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
