cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dinesh Joshi (Jira)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-15623) When running CQLSH with STDIN input, exit with error status code if script fails
Date Sat, 18 Apr 2020 05:30:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-15623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dinesh Joshi updated CASSANDRA-15623:
-------------------------------------
    Status: Ready to Commit  (was: Review In Progress)

+1

> 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: 20m
>  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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message