[
https://issues.apache.org/jira/browse/CASSANDRA-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020511#comment-13020511
]
Jonathan Ellis commented on CASSANDRA-2486:
-------------------------------------------
The compatibility story doesn't change substantially here -- either way you can
do the 99% of operations that don't deal w/ schema changes. But does this make
it easier to build a Hector compatible w/ both 0.7 and 0.8 (by looking at the
server api version), since you can use the same generated Thrift now?
If so then I'll go ahead and commit.
> preserve KsDef backwards compatibility for Thrift clients
> ---------------------------------------------------------
>
> Key: CASSANDRA-2486
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2486
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 0.8
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 0.8
>
> Attachments: 2486.txt
>
>
> CASSANDRA-1263 broke client compatibility; we can't preserve it entirely
> (we'll continue to resturn replication_factor in strategy option rather than
> try to guess somehow if client is an old one) but we can accommodate old
> clients on write and leave the KsDef signature compatible which (I think)
> will make it easier for client authors.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
