You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Matt Ryan (JIRA)" <ji...@apache.org> on 2019/08/08 19:31:00 UTC
[jira] [Updated] (OAK-8536) Update JavaDoc for
completeBinaryUpload() explaining idempotency
[ https://issues.apache.org/jira/browse/OAK-8536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Ryan updated OAK-8536:
---------------------------
Affects Version/s: 1.10.3
1.16.0
> Update JavaDoc for completeBinaryUpload() explaining idempotency
> ----------------------------------------------------------------
>
> Key: OAK-8536
> URL: https://issues.apache.org/jira/browse/OAK-8536
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jackrabbit-api
> Affects Versions: 1.10.3, 1.16.0
> Reporter: Matt Ryan
> Priority: Minor
>
> In OAK-8520 a fix was added in the direct binary upload implementation so that if a client calls {{completeBinaryUpload()}} multiple times with the same upload token, subsequent calls will return the already-uploaded binary without making any change to the backend. It would be good to reflect this case in the JavaDocs for {{JackrabbitValueFactory.completeBinaryUpload()}}.
> (NOTE: Copied from JCR-4463 which was put in the wrong project on accident)
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)