[CASSANDRA-15623] When running CQLSH with STDIN input, exit with error status code if script fails

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.21, 3.11.7, 4.0-beta1, 4.0
• Component/s: Legacy/Tools
• Labels: pull-request-available
• Bug Category: Correctness - API / Semantic Definition
• Severity: Normal
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Since Version: 3.0.21

Source Control Link

https://github.com/apache/cassandra/commit/a738c580224e340f011ffa174a9f1259521120cd

Test and Documentation Plan

Manual testing

• Assignee: Jacob Becker
• Reporter: Jacob Becker

Authors

Jacob Becker

Reviewers

Dinesh Joshi, Jordan West

• Created: 06/Mar/20 07:46
• Updated: 16/Mar/22 13:13
• Resolved: 18/Apr/20 05:30

Description

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.

Issue Links

• relates to: CASSANDRA-15739 dtests fix due to cqlsh behavior change
• links to: GitHub Pull Request #468
• links to: GitHub Pull Request #536