Apache Cassandra

In Chapter 5. Schema and Data Modeling first there is paragraph:

The default cardinality setting is SINGLE. Note, that property keys used on edges and properties have cardinality SINGLE. Attaching multiple values for a single key on an edge or property is not supported.

and then example:

mgmt = graph.openManagement()
follow = mgmt.makeEdgeLabel('follow').multiplicity(MULTI).make()

Hey Crew,

Nice job on gocql, I'm a fan...

For my production services, I could use notification events (via callback or channel) when the gocql client disconnects and reconnects to/from Cassandra. This is useful for higher-level application logic (ie: invoke alarms, stop reading from a durable message queue, etc).

After looking through the code, it looks like the connection information is not p

The .forall pattern is a great way to create an optional filter for a field that could be defined or not:

case class Person(name: String, age: Int)
val nameOpt: Option[String] = Some("Joe")
run { query[Person].filter(p => lift(nameOpt).forall(_ == p.name)) }
// SELECT p.name, p.age FROM Person p WHERE ? IS NULL OR ? = p.name
// (i.e. when nameOpt := None then the `WHERE ? IS NULL`

In the starter class we System.out for "logging" since logback hasn't been enabled yet in this context. This is fine except it makes it a little difficult to grok for Starter related logs.

Add a helper method to prepend levels to the messages to make it easier to identify errors versus info.