Details
-
Improvement
-
Status: Resolved
-
Low
-
Resolution: Duplicate
-
None
-
None
-
None
Description
Currently in CQL3, you can only issue a map or list delete from a delete statement, which is kind of a bummer, because it means you need to span two statements to perform, say, a non-collection column update along with a map-delete.
It would be nice if the set removal syntax was just interpreted as key names for a map, or element values for a list. Removal by list index is a slightly funkier case, but you could do something like listValue - [1,2,3].
Attachments
Issue Links
- duplicates
-
CASSANDRA-3783 Add 'null' support to CQL 3.0
- Resolved