Errata

Cassandra: The Definitive Guide

Errata for Cassandra: The Definitive Guide

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Printed Page xxi
2rd paragraph

In the paragarph of Using Code Examples, there is no link or hint for downloading the code examples, even in Oreilly web site.

 Rick  Jan 02, 2011 
Printed, PDF, ePub Page 1
second paragraph

The quote by Henry Ford is not attributed to him

 Anonymous  Nov 07, 2012 
PDF Page 17
5th paragraph

The text says: "(Amazon, Facebook, Google, Twitter)", but:

1. Facebook has switched to HBase, which is not eventually consistent.
2. Google does not use an eventually consistent data store, as far as I know. Bigtable/Megastore/Spanner/GFS are all consistent.
3. Twitter are using Cassandra, but it would be good to say what for (http://engineering.twitter.com/2010/07/cassandra-at-twitter-today.html).

I guess the thing here is -- when attempting to make a strong case for eventual consistency -- you either need to say where it's in use and/or for what.

Amazon isn't a good enough example because they no longer use Dynamo, and even if they did, they kind of built it, so there's an inherent bias there.

 Anonymous  Nov 29, 2010 
PDF Page 21
image 1-2

There isn't the image 1-2 at page 21 first chapter. i would like to look on my ebook, please.

 Anonymous  Nov 20, 2010 
Printed Page 34
Section "Starting the server"

It says "To start the Cassandra server ..., navigate to the <cassandra-directory>/bin where you unpacked Cassandra" and run "bin/cassandra -f"

It should say "To start the Cassandra server ..., navigate to the <cassandra-directory> where you unpacked Cassandra" and run "bin/cassandra -f" (i.e., navigate to <cassandra-directory> and not <cassandra-directory>/bin)

 Anonymous  Dec 20, 2010 
PDF Page 37
Near bottom of page

Example showed version 0.7.0 beta being used. cassandra-cli commands require a semi-colon at the end of each command. The examples should include a semi-colon.

The semi-colon was not required under version 0.6.8.

 Anonymous  Dec 01, 2010 
Printed, PDF Page 38
second half of the page

When creating a keyspace through the CLI interface, the new syntax (as of version 0.8.0) is

create keyspace MyKeyspace with strategy_options = [{replication_factor:1}];

as indicated by help create keyspace;

 David Garcia Quintas  Jun 03, 2011 
PDF Page 49
keys_cached description, last sentence

" to keep in memory in least-recently-used order."


should be

" to keep in memory in last-recently-used order."


i.e replace "least" with "last" wich makes more sense for a caching algorithm... Correct ?

 hani elabed  Sep 18, 2011 
PDF Page 65
Near bottom of page

The create keyspace attribute replica_placement_strategy should read 'SimpleStrategy' instead of 'RackUnawareStrategy' since the examples are based on version 0.7.

 Anonymous  Dec 02, 2010 
PDF Page 116
2nd and 3rd paragraphs from bottom of page.

The 3rd paragraph from the bottom reads as:
"Next, we need to update the listen address for this machine ...". it's not clear which machine is being referred to. Is it the seed node or the non-seed node.

The 2nd paragraph from the bottom read as:
"Finally, we need to change the address on which our RPC client ...". Same problem. It's not clear which machine is being referred to.

The Riptano's Cassandra documentation referenced from the Cassandra wiki has a clearer explanation.

 Anonymous  Dec 04, 2010 
PDF Page 129
1st paragraph

Near end of 1st paragraph the version number in "we use Cassandra 0.6.7-beta1," should read "we use Cassandra 0.7-beta1,".

 Anonymous  Dec 05, 2010 
PDF Page 226
3rd paragraph

the meaning of "memtable_throughput_in_mb" is different with the "cassandra.yaml".

the book say:
This refers to the maximum number of columns that will be stored in a single memtable before the memtable is flushed to disk as an SSTable. The default value is 0.3, which is approximately 333,000 columns.

in the "cassandra.yaml" wrote:(version: 0.7.0)
memtable_throughput_in_mb:
The maximum size of the memtable before it is flushed. If undefined, 1/8 * heapsize will be used.

that is different!

sorry for me poor English...

 Anonymous  Jan 13, 2011