[
https://issues.apache.org/jira/browse/CASSANDRA-18695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747477#comment-17747477
]
Andres de la Peña commented on CASSANDRA-18695:
-----------------------------------------------
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/2516]|[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/3060/workflows/8f85f880-e39c-41dd-98b9-d44e70a10166]
[j17|https://app.circleci.com/pipelines/github/adelapena/cassandra/3060/workflows/64909dad-f73d-4361-876a-01b4d12eef48]|
> Remove 3.x from the versions checked for prepared statement behaviour
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-18695
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18695
> Project: Cassandra
> Issue Type: Task
> Components: Messaging/Internode
> Reporter: Andres de la Peña
> Assignee: Andres de la Peña
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> CASSANDRA-17248 introduced a different behaviour of prepared statements
> depending on the minimum cluster version. The old behaviour is used when the
> min cluster version is below 3.0.26, 3.11.12 or 4.0.2.
> However, from 5.0 we won't support direct upgrades from 3.0 or 3.11, so we
> can eliminate the checks for those versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
