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

Nachiket Patil updated CASSANDRA-13369:
---------------------------------------
    Description: 
If through CQL, multiple values are specified for a key, grammar parses the map 
and last value for the key wins. This behavior is bad.
e.g. 
```
$ CREATE KEYSPACE "Excalibur" WITH REPLICATION = {'class' : 
'NetworkTopologyStrategy', 'dc1' : 2, 'dc1' : 5};
```
Parsing this statement, 'dc1' gets RF = 5. This can be catastrophic, may even 
result in loss of data. This behavior should not be silent or not be allowed at 
all.  


  was:
If through CQL, multiple values are specified for a key, grammar parses the map 
and last value for the key wins. This behavior is bad.
e.g. 
$ CREATE KEYSPACE "Excalibur" WITH REPLICATION = {'class' : 
'NetworkTopologyStrategy', 'dc1' : 2, 'dc1' : 5};

Parsing this statement, 'dc1' gets RF = 5. This can be catastrophic, may even 
result in loss of data. This behavior should not be silent or not be allowed at 
all.  



> If there are multiple values for a key, CQL grammar choses last value. This 
> should not be silent or should not be allowed.
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-13369
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13369
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL
>            Reporter: Nachiket Patil
>            Assignee: Nachiket Patil
>            Priority: Minor
>             Fix For: 4.0
>
>
> If through CQL, multiple values are specified for a key, grammar parses the 
> map and last value for the key wins. This behavior is bad.
> e.g. 
> ```
> $ CREATE KEYSPACE "Excalibur" WITH REPLICATION = {'class' : 
> 'NetworkTopologyStrategy', 'dc1' : 2, 'dc1' : 5};
> ```
> Parsing this statement, 'dc1' gets RF = 5. This can be catastrophic, may even 
> result in loss of data. This behavior should not be silent or not be allowed 
> at all.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to