Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C5E0C105CC for ; Thu, 13 Mar 2014 12:30:41 +0000 (UTC) Received: (qmail 58975 invoked by uid 500); 13 Mar 2014 12:30:27 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 58794 invoked by uid 500); 13 Mar 2014 12:30:25 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 58578 invoked by uid 99); 13 Mar 2014 12:30:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Mar 2014 12:30:22 +0000 Date: Thu, 13 Mar 2014 12:30:21 +0000 (UTC) From: "Dominique Pfister (JIRA)" To: dev@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (JCR-3733) Asynchronous upload file to S3 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/JCR-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Pfister reassigned JCR-3733: -------------------------------------- Assignee: Dominique Pfister > 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)