[
https://issues.apache.org/jira/browse/CASSANDRA-15623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056615#comment-17056615
]
Jacob Becker commented on CASSANDRA-15623:
------------------------------------------
[~djoshi], [~jrwest], no problem submitting against trunk. Since my local (i.e.
source) branches were named after the target branches, to avoid any possible
confusion, I have created a *new* dedicated PR against trunk:
https://github.com/apache/cassandra/pull/468
Please do your review using the [new
PR|https://github.com/apache/cassandra/pull/468]. In case changes are accepted,
the [original PR|https://github.com/apache/cassandra/pull/467] can serve as a
backport to 3.11.
To explain myself, I had initially submitted against 3.11 because:
* I have been testing against that version;
* I had assumed it was OK to submit against 3.11 since it was actually a bug
fix;
I will keep the clarified workflow in mind, thanks.
> 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
