[
https://issues.apache.org/jira/browse/JCR-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933293#comment-13933293
]
Dominique Pfister commented on JCR-3729:
----------------------------------------
Thanks a lot, Shashank, for providing this extensive patch!
bq. ok. Is there anything i should take care in future?
I guess this error came up because the initial version of the files you changed
was added without svn:eol-style property. Anyway, the post in [1] shows a good
template for these settings.
[1]
http://article.gmane.org/gmane.comp.apache.jackrabbit.devel/369/match=eol+style
> 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
> Assignee: Dominique Pfister
> 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)
