[
https://issues.apache.org/jira/browse/CASSANDRA-9777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654471#comment-14654471
]
Tyler Hobbs commented on CASSANDRA-9777:
----------------------------------------
I think the way [~dkua] is handling it in his branch (using the new location
but warning) is the best option. However, the warning message should explain
what's going on a little better and how the user can resolve the problem. For
example:
{noformat}
Warning: cqlshrc config files were found at both the old location (%s) and the
new location (%s), so the old config file will not be migrated to the new
location, and the new location will be used for now. You should manually
consolidate the config files at the new location and remove the old file.' %
(OLD_CONFIG_FILE, CONFIG_FILE)
{noformat}
Also, warnings should generally be printed to stderr instead of stdout.
> If you have a ~/.cqlshrc and a ~/.cassandra/cqlshrc, cqlsh will overwrite the
> latter with the former
> ----------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-9777
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9777
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jon Moses
> Assignee: David Kua
> Labels: cqlsh
> Fix For: 2.2.x
>
>
> If you have a .cqlshrc file, and a ~/.cassandra/cqlshrc file, when you run
> `cqlsh`, it will overwrite the latter with the former.
> https://github.com/apache/cassandra/blob/trunk/bin/cqlsh#L202
> If the 'new' path exists (~/.cassandra/cqlsh), cqlsh should either WARN or
> just leave the files alone.
> {noformat}
> ~$ cat .cqlshrc
> [authentication]
> ~$ cat .cassandra/cqlshrc
> [connection]
> ~$ cqlsh
> ~$ cat .cqlshrc
> cat: .cqlshrc: No such file or directory
> ~$ cat .cassandra/cqlshrc
> [authentication]
> ~$
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
