[
https://issues.apache.org/jira/browse/CASSANDRA-15623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082765#comment-17082765
]
Dinesh Joshi commented on CASSANDRA-15623:
------------------------------------------
Since I've not heard anything on the dev list, I am inclined to back port your
change with a warning in the {{NEWS.txt}}. Could you please produce two
separate commits one for 3.0 and 3.11 respectively?
> 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
> Assignee: Jacob Becker
> Priority: Normal
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
