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

Erick Ramirez updated CASSANDRA-17667:
--------------------------------------
        Impacts: Clients  (was: None)
    Description: 
I use CQLSH command line utility to load some DDLs. The version of utility I 
use is this:
 
{noformat}[cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native protocol 
v5]{noformat}

Command that loads DDL.cql:

{noformat}
cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql
{noformat}
I have a line in CQL script that breaks the syntax.
{noformat}
INSERT into tablename (key,columnname1,columnname2) VALUES 
('keyName','value1','/value2/*/value3');{noformat}

{{/*}} here is interpreted as start of multi-line comment. It used to work on 
older versions of cqlsh. The error I see looks like this:

{noformat}
SyntaxException: line 4:2 mismatched input 'Update' expecting ')' 
(...,'value1','/value2INSERT into tablename(INSERT into tablename 
(key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line 1:0 
no viable alternative at input '(' ([(]...)
{noformat}

Same behavior while running in interactive mode too. {{/*}} inside a CQL 
statement should not be interpreted as start of multi-line comment.

  was:
I use CQLSH command line utility to load some DDLs.

 

The version of utility I use is this:
 
{{[cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native protocol v5]}}

Command that loads DDL.cql:

 
{code:java}
cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql{code}
I have a line in CQL script that breaks the syntax.
{code:java}
INSERT into tablename (key,columnname1,columnname2) VALUES 
('keyName','value1','/value2/*/value3');{code}
{{ }}
`/*` here is interpreted as start of multi-line comment. It used to work on 
older versions of cqlsh.

 

The error I see looks like this:

 
{code:java}
SyntaxException: line 4:2 mismatched input 'Update' expecting ')' 
(...,'value1','/value2INSERT into tablename(INSERT into tablename 
(key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line 1:0 
no viable alternative at input '(' ([(]...)
 
{code}
 

Same behavior while running in interactive mode too.

 

`/*` inside a CQL statement should not be interpreted as start of multi-line 
comment.


> /* string inside CQL statement is considered as start of multiline statement 
> and breaks syntax
> ----------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17667
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17667
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL/Interpreter
>            Reporter: ANOOP THOMAS
>            Priority: Normal
>
> I use CQLSH command line utility to load some DDLs. The version of utility I 
> use is this:
>  
> {noformat}[cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native 
> protocol v5]{noformat}
> Command that loads DDL.cql:
> {noformat}
> cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql
> {noformat}
> I have a line in CQL script that breaks the syntax.
> {noformat}
> INSERT into tablename (key,columnname1,columnname2) VALUES 
> ('keyName','value1','/value2/*/value3');{noformat}
> {{/*}} here is interpreted as start of multi-line comment. It used to work on 
> older versions of cqlsh. The error I see looks like this:
> {noformat}
> SyntaxException: line 4:2 mismatched input 'Update' expecting ')' 
> (...,'value1','/value2INSERT into tablename(INSERT into tablename 
> (key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line 
> 1:0 no viable alternative at input '(' ([(]...)
> {noformat}
> Same behavior while running in interactive mode too. {{/*}} inside a CQL 
> statement should not be interpreted as start of multi-line comment.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to