[
https://issues.apache.org/jira/browse/COUCHDB-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955800#comment-15955800
]
ASF subversion and git services commented on COUCHDB-2992:
----------------------------------------------------------
Commit a1470e3bdbcb4b98d9cc7f5dc3641a2b008df16b in couchdb-chttpd's branch
refs/heads/COUCHDB-3288-remove-public-db-record from [~vatamane]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-chttpd.git;h=a1470e3 ]
Rename max_document_size to max_http_request_size
`max_document_size` is implemented as `max_http_request_size`. There was no
real check for document size. In some cases the implementation was close enough
of a proxy (PUT-ing and GET-ing single docs), but in some edge cases, like
_bulk_docs requests the discrepancy between request size and document size
could be rather large.
The section was changed accordingly from `couchdb` to `httpd`. `httpd` was
chosen as it applies to both clustered as well as local interface.
There is a parallel effort to implement an actual max_document_size check. The
set of commit should be merged close enough together to allow for a backwards
compatible transition.
COUCHDB-2992
> Add additional support for document size
> ----------------------------------------
>
> Key: COUCHDB-2992
> URL: https://issues.apache.org/jira/browse/COUCHDB-2992
> Project: CouchDB
> Issue Type: Improvement
> Components: Database Core
> Reporter: Tony Sun
>
> Currently, only max_document_size of 64 GB is the restriction for users
> creating documents. Large documents often leads to issues with our indexers.
> This feature will allow users more finer grain control over document size.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
