[ https://issues.apache.org/jira/browse/CASSANDRA-15623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053120#comment-17053120 ]
Jacob Becker commented on CASSANDRA-15623: ------------------------------------------ Also, while this might not be a very proper place to ask this, but I do not really get *why* is the exit code for script errors is 2? Usually 2 is for incorrect arguments or other command syntax errors... To avoid surprises, it would be nice if this "exit code" subject would be documented. > When running CQLSH with STDIN input, exit with error status code if script > fails > -------------------------------------------------------------------------------- > > Key: CASSANDRA-15623 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15623 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Tools > Reporter: Jacob Becker > Priority: Normal > > Assuming CASSANDRA-6344 is in place for years and considering that scripts > submitted with the `-e` option behave in a similar fashion, it is very > surprising that scripts submitted to STDIN (i.e. piped in) always exit with a > zero code, regardless of errors. I believe this should be fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org