[
https://issues.apache.org/jira/browse/COUCHDB-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132132#comment-15132132
]
ASF GitHub Bot commented on COUCHDB-769:
----------------------------------------
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-fabric/pull/33#issuecomment-179768803
@lazedo I think there is no practically need: these options could be
fetched within att_store/2 transparently for the API user during driver resolve
and without abstraction leaks.
Assume we have per-db driver configuration. Where such options will be
stored? First case: in config. Then we do `Driver = get_backend_driver(Db)` and
`Options = get_backend_driver_options(Db, Driver)` right before do any driver
API call. Another case: db options are stored in _metadata db - but this
changes nothing, only configuration backend. What else Options could be passed
here?
> 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)
