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

Jonathan Ellis commented on CASSANDRA-4273:
-------------------------------------------

I'm open to a patch if indeed it doesn't already exist.  Not a fan of putting 
non-error output on stderr tho.
                
> Write auxiliary info to the system's error stream and not to the std output.
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4273
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4273
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API, Tools
>    Affects Versions: 1.1.0, 1.2
>         Environment: Ubuntu 10.04 LTS with Sun Java 1.6.0.26
> Using Cassandra without JNA
>            Reporter: Pantelis Sopasakis
>            Priority: Minor
>              Labels: cassandra-cli
>
> When executing a Cassandra script from the terminal then all output is 
> written to the standard output stream of the system. For example if we create 
> a file called my_script with the following commands:
> use MyKeyspace;
> show schema;
> and we execute it as:
> cassandra-cli < my_script > my.scm
> then the output file my.scm will also contain lines like:
> Connected to: "Test Cluster" on 127.0.0.1/9160
> Welcome to Cassandra CLI version 1.2.0-SNAPSHOT
> Type 'help;' or '?' for help.
> Type 'quit;' or 'exit;' to quit.
> or
> Authenticated to keyspace: MyKeyspace
> Would be good to write such information to the system error stream so that 
> one would be able to do:
> cassandra-cli < my_script > my.scm 2> /dev/null

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to