cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1031) get cassandra version with thrift
Date Wed, 07 Jul 2010 21:48:51 GMT


Eric Evans commented on CASSANDRA-1031:

This patch exposes the release version over Thrift.

I still haven't heard a sensible argument for what a non-management application (i.e. a data
access client) would do with the release version that it could not do with the API version.
In the absence of said argument, the release version seems applicable for management only
(i.e. JMX), and exposing it over Thrift encourages improper use.

I believe the true motivation is for management purposes (that is in fact the genesis of this
ticket), which is why I suggested JMX. I empathize with the  "sucks to use JMX outside Java"
argument, but if this belongs in Thrift, so does everything else we currently expose with


> get cassandra version with thrift 
> ----------------------------------
>                 Key: CASSANDRA-1031
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>         Environment: Linux x86
>            Reporter: Lee Li
>            Assignee: Matthew F. Dennis
>            Priority: Minor
>             Fix For: 0.7
>         Attachments: trunk-1031.txt
> I know I can get thrift API version.
> However, I writing a CLI for Cassandra in Python with readline support,
> and it will supports one-key deploy/upgrade cassandra+thrift remote, 
> I need to get ApacheCassandra version to make sure it has deploy successfully.
> Please add Get **cassandra version** with thrift feature, thank you so much.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message