[
https://issues.apache.org/jira/browse/CASSANDRA-15623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055687#comment-17055687
]
Jacob Becker commented on CASSANDRA-15623:
------------------------------------------
[~jrwest], as discussed, here comes the patch:
https://github.com/apache/cassandra/pull/467
I assume you do not do any (direct) merges at GitHub, but at least to be clear
on the target branch, I think an MR there is still useful. In case you are fine
with the changes, I guess I could *port* the fix to other branches (simply
merging will not do. files are too different, even for neighboring branches)
and create the respective MRs, though in this case I would expect you to tell
me a list of branches you would like to port to.
> 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: [email protected]
For additional commands, e-mail: [email protected]
