couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filipe Manana (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (COUCHDB-1004) list_to_existing_atom is too restrictive as used by couch_rep
Date Wed, 20 Apr 2011 10:49:05 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Filipe Manana resolved COUCHDB-1004.
------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.2)

Applied Adam's suggestion (use couch_util:to_existing_atom/1) to 1.0.x and 1.1.x.
Trunk does not suffer from this issue.

> list_to_existing_atom is too restrictive as used by couch_rep
> -------------------------------------------------------------
>
>                 Key: COUCHDB-1004
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1004
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Replication
>         Environment: erlang
>            Reporter: Bob Dionne
>            Priority: Minor
>             Fix For: 1.0.3, 1.1
>
>         Attachments: COUCHDB-1004.patch
>
>
> We'd like to additional information to db_info in BigCouch, such as the Q and N constants
for a given database. This causes replication to fail when replicating from BigCouch to CouchDB
due to the use of list_to_existing_atom in couch_rep:dbinfo(...
> The claim is that list_to_atom pollutes the atoms table, however superficial testing
indicates this is not the case, list_to_atom when called repeatedly seems to work fine. If
this is true then consider reverting list_to_existing_atom back to list_to_atom.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message