[
https://issues.apache.org/jira/browse/COUCHDB-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132173#comment-15132173
]
ASF GitHub Bot commented on COUCHDB-769:
----------------------------------------
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-fabric/pull/33#issuecomment-179780756
@lazedo
`Options` argument assumes that it will be passed from the outside. Who
will form it and how? And if it contains some url to there attachment have to
be stored (by your example, as I get it right), how it would be preserved on
the following attachment read? Have to be we need to store these options
somewhere and link them by the database-document-attachment triple id. In
`att_store` we already have all these information that need to lookup such
options (assuming that they are stored outside of the document).
Per-attachment configuration involves custom attachment stub fields
feature, so they all will be available for the passed Doc argument (in anyway
it's a reasonable to store them within the document itself). But that would be
a question how to store private information there and how they should be
replicated.
> 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)
