[
https://issues.apache.org/jira/browse/CASSANDRA-17602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17553937#comment-17553937
]
Stefan Miklosovic edited comment on CASSANDRA-17602 at 6/14/22 7:24 AM:
------------------------------------------------------------------------
Huh, I dont get it, this is not yaml.
I was explicitly asking this:
I would just remove it all right now - no "transition" / deprecation period.
Brandon said:
I think that makes sense since it's no longer necessary in 4.0.
What I do not like about this workflow is that the ticket is back in "open"
because "you said so". I think the hierarchy is pretty flat here. What it would
be like for you if I started to open your tickets?
If we ever want to "deprecate it" (which does not make sense because it should
not be there in the first place at all), I am against reverting this - what I
can do is to create new patch which would re-introduce this flag and it would
do basically nothing - it would just alias to storage port internally. However
that does not make sense either because once we have to just remove it. What do
you mean by "informing the users"? Mentioning it in NEWS.txt ?
was (Author: smiklosovic):
Huh, I dont get it, this is not yaml.
I was explicitly asking this:
I would just remove it all right now - no "transition" / deprecation period.
Brandon said:
I think that makes sense since it's no longer necessary in 4.0.
What I do not like about this workflow is that the ticket is back in "open"
because "you said so". I think the hierarchy is pretty flat here. What it would
be like for you if I started to open your tickets?
> 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.5, 4.1-beta, 4.2
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
