cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Ploetz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7131) Add command line option for cqlshrc file path
Date Wed, 03 Sep 2014 13:43:51 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119861#comment-14119861
] 

Aaron Ploetz commented on CASSANDRA-7131:
-----------------------------------------

The problem with implementing this one, is that the cqlshrc path (CONFIG_FILE) is defined
so early on in cqlsh, that it happens before the command line arguments are parsed.  There
are two ways to solve this.  Either we parse a new {{--cqlshrc}} argument early and independently,
or we move the {{parser = optparse.OptionParser(...}} section (and dependencies) above the
definition of CONFIG_FILE.

A less-invasive change would be to move the definition of HISTORY_DIR, CONFIG_FILE, and HISTORY
down below the parsing section.  I'm thinking that this approach is probably the better option,
unless someone has a strong argument against it.

> Add command line option for cqlshrc file path
> ---------------------------------------------
>
>                 Key: CASSANDRA-7131
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7131
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Jeremiah Jordan
>            Priority: Trivial
>              Labels: lhf
>
> It would be nice if you could specify the cqlshrc file location on the command line,
so you don't have to jump through hoops when running it from a service user or something.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message