"What kinds of things would it be good to know for an interview?"
The underlying storage engine and how CQL3 maps to it. It's more than important, it's crucial. Knowing what you do and what you can't with CQL3 is not sufficient. On Tue, Jul 22, 2014 at 9:20 PM, jcllings <jclli...@gmail.com> wrote: > So It seems that: > > 1. There are indeed a few (3-4) mapping schemes. > 2. CQL isn't very hard and represents a subset of (ANSI?) SQ92. > > Both of these are validated based on further research and list guidance. > > It appears that learning Cassandra from an application developers > perspective essentially means learning what you can't do at all and > learning what you can't do directly that you could do with an RDMBS. > This and keys and maybe a thing or two about replication strategies and > you should be good to go. Does this seem accurate? > > What kinds of things would it be good to know for an interview? > > Jim C. > >
