[
https://issues.apache.org/jira/browse/COUCHDB-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071105#comment-15071105
]
ASF GitHub Bot commented on COUCHDB-769:
----------------------------------------
Github user gilv commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/82#issuecomment-167132132
@kxepal : you asked to "Is it possible to decouple logic of working with
external attachments from the logic that works with internal ones? Mixing them
makes quite hard to follow the track."
Can you please explain me what would you like to see exactly? Perhaps i
didn't understand it.
Currently fabric_attachment_handler is the one that responsible to store
attachments externally. This module does't really care if it's internal or
external, they both go to the same object store.
> 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)
