[
https://issues.apache.org/jira/browse/CASSANDRA-17602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537671#comment-17537671
]
Stefan Miklosovic edited comment on CASSANDRA-17602 at 5/16/22 5:18 PM:
------------------------------------------------------------------------
Do we want to log some message that ssp is deprecated and effectively ignored
and only sp is used? In other words, do we still want react on ssp flag but do
nothing or we just error out as that option would not be recognized anymore?
We would need to get back to this in 4.0.6, 4.1.1 and 4.2 to get rid of that
fully.
I would just remove it all right now - no "transition" / deprecation period.
was (Author: smiklosovic):
Do we want to log some message that ssp is deprecated and effectively ignored
and only sp is used? In other words, do we still want react on ssp flag but do
nothing or we just error out as that option would not be recognized anymore?
> sstableloader not respecting conf-path flag
> -------------------------------------------
>
> Key: CASSANDRA-17602
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17602
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
> Reporter: Aswin Karthik
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.0.x, 4.1-beta
>
>
> Hello,
> sstableloader does not seem to respect the config file flag (-f) and the
> storage port flag.
>
> We run our cluster on a different storage port with encryption. We construct
> a YAML with {{server_encryption_options}} and {{client_encryption_options}}
> and pass the storage port flag (both {{-sp}} and {{-ssp}}).
>
> However, we noticed that both the storage port flag and encryption settings
> are getting picked from the default config file {{conf/cassandra.yaml}} and
> ends up connecting to 7000 port unencrypted. As a workaround, we have added
> the storage port configuration to the YAML and copy our configuration file
> and overwrite the {{conf/cassandra.yaml}} and it is working now.
>
> Also to be noted that using the {{-f}} works in Cassandra 3.x. The bug seems
> to be present in 4.x versions only.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
