[
https://issues.apache.org/jira/browse/JCR-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominique Pfister updated JCR-3733:
-----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Patch revised and committed in revision 1577127 to trunk.
> Asynchronous upload file to S3
> ------------------------------
>
> Key: JCR-3733
> URL: https://issues.apache.org/jira/browse/JCR-3733
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-core
> Affects Versions: 2.7.4
> Reporter: Shashank Gupta
> Assignee: Dominique Pfister
> Fix For: 2.7.5
>
>
> S3DataStore Asynchronous Upload to S3
> The current logic to add a file record to S3DataStore is first add the file
> in local cache and then upload that file to S3 in a single synchronous step.
> This feature contemplates to break the current logic with synchronous adding
> to local cache and asynchronous uploading of the file to S3. Till
> asynchronous upload completes, all data (inputstream, length and
> lastModified) for that file record is fetched from local cache.
> AWS SDK provides upload progress listeners which provides various callbacks
> on the status of in-progress upload.
> As of now customer reported that write performance of EBS based Datastore is
> 3x better than S3 DataStore.
> With this feature, the objective is to have comparable write performance of
> S3 DataStore.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
