@Bruce I do see the patch applied and the aws-ext is present on the jackrabbit trunk. Please see [0]
@Bertrand, thanks for pointing to the jackrabbit-aws-ext. I have configured it as specified at [1] . Can you please cite an example on how to use it ? Specifically, how to get its instance and then use it in context of sling. Thanks [0] - http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-aws-ext/?pathrev=1521876 [1] - https://github.com/apache/jackrabbit/tree/trunk/jackrabbit-aws-ext On Fri, Jan 23, 2015 at 12:17 AM, Bruce Edge <bruce.e...@nextissuemedia.com> wrote: > > > >Note that > >http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-aws-ext > >implements S3 storage for Jackrabbit, you might be able to reuse some > >of that. > > What would be required to pull jackrabbit-aws-ext into the sling tree as a > configurable option? > IMO this would be a valuable addition, i.e.: to be able to deploy with an > S3 backend. S3 storage is an order of magnitude cheaper than EBS volumes > in AWS. > > > connuser1 - If you do look into it, maybe I¹m reading this wrong, but it > looks like the jackrabbit-aws-ext implementation has a patch (JCR-3651) > that¹s been stuck in limbo [1] since 2013 > At least, it¹s status is ³Patch available². Did it just not get marked as > applied? > > > [1] https://issues.apache.org/jira/browse/JCR-3651 > > -Bruce > >
