[
https://issues.apache.org/jira/browse/JCR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashank Gupta updated JCR-3729:
--------------------------------
Attachment: JCR-3729_V2.patch
attached patch version 2.
>What was the reason for moving them to jackrabbit-data?
the code they are testing reside in jackrabbit-data. for e.g. CachingDataStore
resides in jackrabbit-data but there are no tests corresponding to it.
>fixing the svn:eol-style problem, I was able to apply the patch.
ok. Is there anything i should take care in future?
>You introduced a cyclic dependency between jackrabbit-core and jackrabbit-data.
After refactoring test classes, i missed to build complete jackrabbit project
but built the individual projects. sorry about this.
>You further introduced a class o.a.j.core.util.NamedThreadFactory.java in
>jackrabbit-data and this package name
changed package to o.a.j.core.data.util. thnx
>Hm, I disagree: in file S3Backend you (or your IDE) moved instance variables
>in front of class variables.
corrected. thnx.
> 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, JCR-3729_V2.patch
>
>
> Following optimizations can be done on S3 Datastore based on customer's/S3
> engineers feedback.
> * 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
(v6.2#6252)
