--- On Sat, 8/4/12, Brian O'Neill wrote:
> From: Brian O'Neill
> Subject: A Big Data Trifecta: Storm, Kafka and Cassandra
> To: user@cassandra.apache.org
> Date: Saturday, August 4, 2012, 4:41 AM
> Philip,
>
> I figured I would reply via blog post. =)
> http://brianoneill.blogspot.com/2012/08/a
Thanks. That was what I expected, but wanted to confirm.
On Aug 4, 2012 11:24 AM, "Dave Brosius" wrote:
> There is a second (system managed) column family for each secondary index,
> so any write to a field that is indexed causes two writes, one to the main
> column family, and another to the ind
There is a second (system managed) column family for each secondary
index, so any write to a field that is indexed causes two writes, one to
the main column family, and another to the index column family, where in
this index column family the key is the value of the secondary column,
and the va
Morning,
Was reading up on secondary indexes and on the Datastax post about them, it
mentions the additional management overhead, and also that if you alter an
existing column family, that data will be updated in the background. But
how do secondary indexes affect write performance?
If the answe
Philip,
I figured I would reply via blog post. =)
http://brianoneill.blogspot.com/2012/08/a-big-data-trifecta-storm-kafka-and.html
That blog post shows how we pieced together Kafka and Cassandra (via Storm).
With LinkedIn behind Kafka, it is well supported. They use it in
production. (and most l
