[
https://issues.apache.org/jira/browse/COUCHDB-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15084964#comment-15084964
]
ASF GitHub Bot commented on COUCHDB-769:
----------------------------------------
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-fabric/pull/33#issuecomment-169215816
@gilv
2. I'm afraid there is no any document that describes whole set of rules. I
want to setup elvis to define and control that, but it's a future. For now,
better just follow the comments.
3. Tests need to cover whole attachments API to ensure that everything
works same as before + I think some test with replication would be nice to have
to see how it goes. Here is the main question is how to ensure that swift
integration code is really works. I'm not sure that it's possible to verify
that without Open Stack cluster. Hopefully, today, we have docker thing for the
resque.
> Store large attachments external to the .couch file
> ---------------------------------------------------
>
> Key: COUCHDB-769
> URL: https://issues.apache.org/jira/browse/COUCHDB-769
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core
> Reporter: Robert Newson
> Assignee: Adam Kocoloski
> Attachments: external_attachments_alpha.patch
>
>
> For attachment-heavy applications storing the attachments in separate files
> significantly eases compaction problems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
