[
https://issues.apache.org/jira/browse/CASSANDRA-15750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-15750:
--------------------------------------
Change Category: Semantic
Complexity: Challenging
Status: Open (was: Triage Needed)
The main things I would worry about are the following
1) binary compatibility for any API exposed in user land (aka, anything not run
by CassandraDaemon, which also means anyone who depends on cassandra-all);
based off other discussions it sounds like 4.x will add a binary comparable
layer making all public classes in 3.x binary comparable with 4.x.
2) semantic compatibility. Even if the API has the same signature does it act
the same way? A simple example is CASSANDRA-15637, even though there were
similar apis they acted very differently which caused a massive performance
regression to CqlInputFormat
3) stability and longevity. If someone gets their client by depending on
cassandra-all, and their JVM is up for 1 year actively or passively making
requests to Cassandra, it should be fine.
All three of these are large tasks given the fact 4.x is a large change, so I
would be hesitant about upgrading to it any time soon.
> Upgrade Cassandra Java Driver to 4.6
> ------------------------------------
>
> Key: CASSANDRA-15750
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15750
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Eduard Tudenhoefner
> Assignee: Eduard Tudenhoefner
> Priority: Normal
> Fix For: 4.0-beta, 4.0-rc
>
>
> Before releasing C* 4.0 I think it would be a good idea to upgrade to the
> latest Cassandra Java Driver that is being used internally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
