[
https://issues.apache.org/jira/browse/CASSANDRA-15623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17054803#comment-17054803
]
Jacob Becker commented on CASSANDRA-15623:
------------------------------------------
[~jrwest], after taking a look at the code, I would say yes, I will provide a
patch. I believe I can manage within a few days.
As for the exit code being 1 or 2, it is debatable indeed as, AFAIK, there is
no (generic) specification in this regard. What is truly important is that it
is not 0 (and it is not), so I wasn't sure if the subject is even worth a new
ticket. I personally can live just fine with 2, I mentioned it only because,
from my experience, anything above 1 usually has some underlying reason
(ideally - explained in documentation); from what I can tell, there is no such
reason in this case (especially considering the script *never* exits with 1)
and no mention in the documentation.
> 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
