[
https://issues.apache.org/jira/browse/CASSANDRA-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885772#action_12885772
]
Eric Evans commented on CASSANDRA-1031:
---------------------------------------
{quote}
how would you make a client supporting both 0.6 (String keys) and 0.7 (byte[]
keys) otherwise? call methods that only exist in one or the other? i suppose
that's workable but it's a little ugly.
{quote}
These are differences in the API. Do you have in mind some way in which the
release version better indicates this condition than the API version?
{quote}
what are the downsides to exposing it over thrift?
{quote}
That it encourages people to use it for gauging API compatibility instead of
using the more capable API version (more capable because it does not move in
lock-step with releases, and because it also encodes the type of change).
> get cassandra version with thrift
> ----------------------------------
>
> Key: CASSANDRA-1031
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1031
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Environment: Linux x86
> Reporter: Lee Li
> Assignee: Matthew F. Dennis
> Priority: Minor
> Fix For: 0.7
>
>
> 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.
