[
https://issues.apache.org/jira/browse/COUCHDB-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132212#comment-15132212
]
ASF GitHub Bot commented on COUCHDB-769:
----------------------------------------
Github user lazedo commented on the pull request:
https://github.com/apache/couchdb-fabric/pull/33#issuecomment-179789279
@kxepal maybe i'm missing the objective of this feature. as i see it, a
external attachment would still create the stub information about how to reach
the `real` attachment. the `stub`would have the information needed to get the
attachment back, so, you would need to store the `driver` in case the
configuration is changed and you start using another driver but still want to
reach the already stored attachments. the `options` would allow more
flexibility to the driver creating the necessary stub information needed to get
the attachment back and also to choose which driver we want for the attachment.
> 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)
