[CASSANDRA-12189] $$ escaped string literals are not handled correctly in cqlsh

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.8
• Component/s: Legacy/Tools
• Severity: Normal
• Since Version: 3.0.0
• Assignee: Mike Adamson
• Reporter: Mike Adamson

Authors

Mike Adamson

Reviewers

Alex Petrov

• Created: 13/Jul/16 09:33
• Updated: 15/Jul/20 18:07
• Resolved: 20/Jul/16 14:05

Description

The syntax rules for pg ($$) escaped string literals in cqlsh do not match the lexer rule for this type in Lexer.g.

The unclosedPgString rule is not correctly matching pg string literals in multi-line statements so:

INSERT INTO test.test (id) values (
...$$<xml/>

fails with a syntax error at the forward slash.

Both pgStringLiteral and unclosedPgString fail with the following string

$$a$b$$

where this is allowed by the CQL lexer rule.

Issue Links

• is duplicated by: CASSANDRA-12187 $$ escaped string literals are not handled correctly in cqlsh
• relates to: CASSANDRA-15948 Multiple failures in cqlsh_tests.test_cqlsh.TestCqlsh