[
https://issues.apache.org/jira/browse/CASSANDRA-16736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382273#comment-17382273
]
Ekaterina Dimitrova commented on CASSANDRA-16736:
-------------------------------------------------
I just found CASSANDRA-15985 in the meanwhile. I guess we can cherry-pick at
least the already provided fixes there.
CC [~mck], not sure what are the expectations around 2.2 before moving it out
of support. Is there any list of actions to be taken or so?
> CQL shell should prefer newer TLS version by default
> ----------------------------------------------------
>
> Key: CASSANDRA-16736
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16736
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/cqlsh
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 2.2.x
>
>
> This is a follow up to CASSANDRA-16695 where a patch was committed to 3.0,
> 3.11, 4.0 and trunk.
> As part of it we saw that CQL shell python DTests are failing due to config
> issues for version 2.2.
> As part of the current ticket we need to produce a fix to be able to run the
> CQL shell tests and verify and apply the patch from CASSANDRA-16695 to
> Cassandra 2.2
--
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
