cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Wong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6344) When running CQLSH with file input, exit with error status code if script fails
Date Sat, 19 Apr 2014 20:34:16 GMT

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

Sebastian Wong commented on CASSANDRA-6344:
-------------------------------------------

I believe it's Cassandra 2.1. The latest commit on the branch I'm on is:

commit 6e97178a50d1cc9a6817653e463ef5f0cf132873
Merge: f04b775 6658a6e
Author: Yuki Morishita <yukim@apache.org>
Date:   Sat Apr 12 15:22:55 2014 -0500

    Merge branch 'cassandra-2.1' into trunk

> When running CQLSH with file input, exit with error status code if script fails
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6344
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6344
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Branden Visser
>              Labels: lhf
>             Fix For: 1.2.17, 2.0.8, 2.1 beta2
>
>         Attachments: CASSANDRA-6344.txt
>
>
> Just thought it would be nice if the cqlsh process would exit with an error status code
if there are errors in the script, since it is the only thing the cqlsh process does when
executing.
> Preferably a predictable status code could be used for a script error to discern it from
some other odd error (i.e., don't use `1` because that could be many things). Maybe `2` or
something.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message