[jira] [Updated] (CASSANDRA-17602) sstableloader not respecting conf-path flag

["Aswin Karthik (Jira)" <ji...@apache.org>]

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

Aswin Karthik updated CASSANDRA-17602:
--------------------------------------
    Summary: sstableloader not respecting conf-path flag  (was: sstableloader not respecting conf-file flag)

> 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
>            Priority: Normal
>             Fix For: 4.0.x
>
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org