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 20:06:00 UTC
[jira] [Commented] (OAK-8536) Update JavaDoc for
completeBinaryUpload() explaining idempotency
[ https://issues.apache.org/jira/browse/OAK-8536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903279#comment-16903279 ]
Matt Ryan commented on OAK-8536:
--------------------------------
Fixed in [r1864731|https://svn.apache.org/viewvc?view=revision&revision=1864731].
> 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
> Assignee: Matt Ryan
> Priority: Minor
> Fix For: 1.18.0, 1.10.4
>
>
> 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)