couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (COUCHDB-904) No method to detect view server VM version
Date Wed, 19 Oct 2011 22:55:11 GMT

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

Randall Leeds updated COUCHDB-904:
----------------------------------

    Fix Version/s: 2.0

I'm going to say this is a good one for 2.0. Breaks protocol, but also a major version release
is a good time to install these sorts of forward-compatibility features.
                
> No method to detect view server VM version
> ------------------------------------------
>
>                 Key: COUCHDB-904
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-904
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: JavaScript View Server
>            Reporter: Paul Joseph Davis
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: patch.txt
>
>
> There's currently no way to tell what version of the view server is being used. Ie, the
JS VM (Or Python, or Ruby, etc) that is being used. Just occurred to me it could be useful
for debugging things that work one place and not another.
> A proposed simple fix would be to have the view server protocol dictate that when a server
boots up it spits out a line like:
> {"version": OPAQUE_STRING} that gets stored in a view_server_versions section in the
config or some such.

--
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

        

Mime
View raw message