You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Alexander Shorin (JIRA)" <ji...@apache.org> on 2012/05/26 00:22:23 UTC

[jira] [Created] (COUCHDB-1484) Document _id length overflow

Alexander Shorin created COUCHDB-1484:
-----------------------------------------

             Summary: Document _id length overflow
                 Key: COUCHDB-1484
                 URL: https://issues.apache.org/jira/browse/COUCHDB-1484
             Project: CouchDB
          Issue Type: Bug
          Components: Database Core
    Affects Versions: 1.2, 1.1.1, 1.3
            Reporter: Alexander Shorin
            Priority: Blocker


CouchDB allows to create document with ids longer that max length of URL (avg. 2000 chars). Such documents are unavailable for GET/HEAD/DELETE requests.  However, you still able to operate with them via POST/PUT requests, views and replication works fine for them.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (COUCHDB-1484) Document _id length overflow

Posted by "Robert Newson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COUCHDB-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Newson resolved COUCHDB-1484.
------------------------------------

    Resolution: Won't Fix

While I don't think it's very sensible to have document identifiers of these lengths, unless there is something that becomes impossible, I don't think we should do anything.

Since documents can be created, updated, deleted, and retrieved using a POST call, I don't think this is a problem (and certainly not a release blocking issue).

Reopen if you've encountered more serious errors with very long identifiers other than encountering the practical URI length limit of your user agent.

                
> Document _id length overflow
> ----------------------------
>
>                 Key: COUCHDB-1484
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1484
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 1.1.1, 1.2, 1.3
>            Reporter: Alexander Shorin
>            Assignee: Robert Newson
>            Priority: Blocker
>
> CouchDB allows to create document with ids longer that max length of URL (avg. 2000 chars). Such documents are unavailable for GET/HEAD/DELETE requests.  However, you still able to operate with them via POST/PUT requests, views and replication works fine for them.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (COUCHDB-1484) Document _id length overflow

Posted by "Robert Newson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COUCHDB-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Newson reassigned COUCHDB-1484:
--------------------------------------

    Assignee: Robert Newson
    
> Document _id length overflow
> ----------------------------
>
>                 Key: COUCHDB-1484
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1484
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 1.1.1, 1.2, 1.3
>            Reporter: Alexander Shorin
>            Assignee: Robert Newson
>            Priority: Blocker
>
> CouchDB allows to create document with ids longer that max length of URL (avg. 2000 chars). Such documents are unavailable for GET/HEAD/DELETE requests.  However, you still able to operate with them via POST/PUT requests, views and replication works fine for them.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira