You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Jan Lehnardt (JIRA)" <ji...@apache.org> on 2009/11/04 18:05:32 UTC
[jira] Commented: (COUCHDB-559) 0.9.1 pushing to 0.10.0 fails b/c
of list_to_existing_atom("disk_format_version").
[ https://issues.apache.org/jira/browse/COUCHDB-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773562#action_12773562 ]
Jan Lehnardt commented on COUCHDB-559:
--------------------------------------
Can we look at the user agent string and have 0.10 omit disk_format_version if the agent reports a 0.9.x couch?
> 0.9.1 pushing to 0.10.0 fails b/c of list_to_existing_atom("disk_format_version").
> ----------------------------------------------------------------------------------
>
> Key: COUCHDB-559
> URL: https://issues.apache.org/jira/browse/COUCHDB-559
> Project: CouchDB
> Issue Type: Bug
> Components: Replication
> Affects Versions: 0.10
> Reporter: Adam Kocoloski
>
> The atom disk_format_version doesn't appear in 0.9.1, but in 0.10.0 it's part of the info returned by GET /dbname. If an 0.9.1 server tries to push to 0.10.0, it'll fail trying to decode "disk_format_version" into an existing atom.
> Not sure at this point about the best workaround.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.