You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Adam Kocoloski (JIRA)" <ji...@apache.org> on 2009/05/17 14:25:45 UTC
[jira] Created: (COUCHDB-352) Replicate documents and attachments
with extremely long IDs
Replicate documents and attachments with extremely long IDs
-----------------------------------------------------------
Key: COUCHDB-352
URL: https://issues.apache.org/jira/browse/COUCHDB-352
Project: CouchDB
Issue Type: New Feature
Components: Database Core
Reporter: Adam Kocoloski
Priority: Minor
In COUCHDB-243 we concluded that the replicator should try to play nice with documents and attachments that have names longer than MochiWeb can handle. Opening this case to track how we might go about that.
The replicator already handles documents with lots of revisions to replicate by chunking the rev list and combining the results from multiple requests. We obviously can't play the same game with document IDs and attachment names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-352) Replicate documents and attachments
with extremely long IDs
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Joseph Davis updated COUCHDB-352:
--------------------------------------
Skill Level: Regular Contributors Level (Easy to Medium)
> Replicate documents and attachments with extremely long IDs
> -----------------------------------------------------------
>
> Key: COUCHDB-352
> URL: https://issues.apache.org/jira/browse/COUCHDB-352
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core
> Reporter: Adam Kocoloski
> Priority: Minor
>
> In COUCHDB-243 we concluded that the replicator should try to play nice with documents and attachments that have names longer than MochiWeb can handle. Opening this case to track how we might go about that.
> The replicator already handles documents with lots of revisions to replicate by chunking the rev list and combining the results from multiple requests. We obviously can't play the same game with document IDs and attachment names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.