jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Pfister (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3729) S3 Datastore optimizations
Date Wed, 12 Mar 2014 10:25:44 GMT

    [ https://issues.apache.org/jira/browse/JCR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931614#comment-13931614

Dominique Pfister commented on JCR-3729:

bq. since changes are too large i advise to look at full source code.

I tried applying your patch to the the current trunk, but still get a huge amount of rejected
changes: I noticed that the files concerned have CR+LF in my checkout although I'm working
on *nix. Apparently, a lot of files in jackrabbit-data have no svn:eol-style set, and are
therefore treated as is which confuses the patch tool.

> S3 Datastore optimizations
> --------------------------
>                 Key: JCR-3729
>                 URL: https://issues.apache.org/jira/browse/JCR-3729
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: 2.7.4
>            Reporter: Shashank Gupta
>             Fix For: 2.7.5
>         Attachments: JCR-3729.patch, JCR-3729_V1.patch
> Following optimizations can be done on S3 Datastore based on customer's/S3 engineers
> *  Use object keys to create partitions in S3 automatically.
> *  Multi-threaded migration of binary files from FileSystem to S3 datastore
> *  Externalize S3 endpoints.
> *  Asynchronous upload file to S3
> *  Slow Startup Of Instance

This message was sent by Atlassian JIRA

View raw message