Yes, your remark is correct. However, once CASSANDRA-7396 (right now in 4.0 trunk) get released, you will be able to get a slice of map values using their (sorted) keys
SELECT map[fromKey ... toKey] FROM TABLE ... Needless to say, it will be also possible to get a single element from the map by its key with SELECT map[key] syntax It will work exactly like clustering columns storage engine-wise. On Wed, Nov 15, 2017 at 5:12 PM, eugene miretsky <eugene.miret...@gmail.com> wrote: > Hi, > > What would be the tradeoffs between using > > 1) Map > > ( > > id UUID PRIMARY KEY, > > myMap map<int,text> > > ); > > 2) Clustering key > > ( > > id UUID PRIMARY KEY, > > key int, > > val text, > > PRIMARY KEY (id, key)) > > ); > > My understanding is that maps are stored very similarly to clustering > columns, where the map key is part of the SSTable's column name. The main > difference seems to be that with maps all the key/value pairs get retrieved > together, while with clustering keys we can retrieve individual rows, or a > range of keys. > > Cheers, > Eugene >
