[
https://issues.apache.org/jira/browse/CASSANDRA-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Wong updated CASSANDRA-6344:
--------------------------------------
Attachment: CASSANDRA-6344.txt
I oversimplified the problem on my first pass through the code. Setting the
error condition to true when EOFError is thrown is incorrect and the program
will always exit with error code 2. This version of the patch goes through the
query execution path and sets the error condition to True whenever an error
during parsing has been found.
> 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)
