You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Bohdan Siryk (Jira)" <ji...@apache.org> on 2026/02/02 09:13:00 UTC
[jira] [Commented] (CASSANDRA-21146) Guardrail for client driver versions
[ https://issues.apache.org/jira/browse/CASSANDRA-21146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055875#comment-18055875 ]
Bohdan Siryk commented on CASSANDRA-21146:
------------------------------------------
> Configurable minimum supported driver version, scoped by driver type (e.g., Java).
Is "By type" meant to be the *DRIVER_NAME* option according to the protocol? To the best of my knowledge, there is no established naming convention for the drivers - please correct me if I'm wrong. It should also account for this, as naming is very different: java driver name - {_}Apache Cassandra Java Driver{_}; go driver name - {_}github.com/apache/cassandra-gocql-driver{_}.
> Guardrail for client driver versions
> ------------------------------------
>
> Key: CASSANDRA-21146
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21146
> Project: Apache Cassandra
> Issue Type: Improvement
> Reporter: Brad Schoening
> Priority: Normal
>
> Many application teams lag multiple years behind on Cassandra driver upgrades, which increases operational risk and complicates cluster upgrades and support. Today, there is no native mechanism to discourage or prevent clients from connecting with severely outdated drivers.
> Proposed New Feature
> Introduce an optional server-side guardrail that allows operators to block client connections using drivers older than a configured minimum version (for example, rejecting Java drivers earlier than 3.11.5).
> Key Characteristics
> * Disabled by default.
> * Configurable minimum supported driver version, scoped by driver type (e.g., Java).
> * Intended primarily for non-production environments (dev / UAT), where stricter enforcement can be applied ahead of production rollouts.
> * Provides a clear, early failure signal to application teams that a driver upgrade is required.
> Benefits
> * Forces proactive driver upgrades before cluster upgrades.
> * Reduces risk from unsupported or poorly tested legacy drivers.
> * Improves overall fleet hygiene and operational predictability.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org