You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Matt Ryan (JIRA)" <ji...@apache.org> on 2019/08/08 20:09:00 UTC
[jira] [Commented] (JCR-4463) Update JavaDoc for
completeBinaryUpload explaining idempotency
[ https://issues.apache.org/jira/browse/JCR-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903281#comment-16903281 ]
Matt Ryan commented on JCR-4463:
--------------------------------
Fixed in [r1864732|https://svn.apache.org/viewvc?view=revision&revision=1864732].
> Update JavaDoc for completeBinaryUpload explaining idempotency
> --------------------------------------------------------------
>
> Key: JCR-4463
> URL: https://issues.apache.org/jira/browse/JCR-4463
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-api
> Reporter: Matt Ryan
> Assignee: Matt Ryan
> Priority: Minor
> Fix For: 2.18.3
>
>
> 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()}}.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)