[ 
https://issues.apache.org/jira/browse/CASSANDRA-14299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Podkowinski updated CASSANDRA-14299:
-------------------------------------------
         Assignee: Stefan Podkowinski
    Fix Version/s: 4.x
                   3.11.x
           Status: Patch Available  (was: Open)

Looks like a merge oversight in 
[6d429cd|https://github.com/apache/cassandra/commit/6d429cd]. Trivial fix is 
linked, do you mind take a look [~ifesdjeen]?

> cqlsh: ssl setting not read from cqlshrc in 3.11 
> -------------------------------------------------
>
>                 Key: CASSANDRA-14299
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14299
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Christian Becker
>            Assignee: Stefan Podkowinski
>            Priority: Major
>             Fix For: 3.11.x, 4.x
>
>
> With CASSANDRA-10458 an option was added to read the {{--ssl}} flag from 
> cqlshrc, however the commit seems to have been incorrectly merged or the 
> changes were dropped somehow.
> Currently adding the following has no effect:
> {code:java}
> [connection]
> ssl = true{code}
> When looking at the current tree it's obvious that the flag is not read: 
> [https://github.com/apache/cassandra/blame/cassandra-3.11/bin/cqlsh.py#L2247]
> However it should have been added with 
> [https://github.com/apache/cassandra/commit/70649a8d65825144fcdbde136d9b6354ef1fb911]
> The values like {{DEFAULT_SSL = False}}  are present, but the 
> {{option_with_default()}} call is missing.
> Git blame also shows no change to that line which would have reverted the 
> change.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to