Hello all,
Work has begun on the second edition! Keep hitting me up with ideas.
In particular I am looking for someone who has done work with
flume+Cassandra and pig+Cassandra. Both of these things topics will be
covered to some extent in the second edition, but these are two
instances in which
On Wed, Jun 27, 2012 at 5:11 PM, Aaron Turner synfina...@gmail.com wrote:
Honestly, I think using the same terms as a RDBMS does
makes users think they're exactly the same thing and have the same
properties... which is close enough in some cases, but dangerous in
others.
The point is that
Great stuff!!!
On Tue, Jun 26, 2012 at 5:25 PM, Edward Capriolo edlinuxg...@gmail.comwrote:
Hello all,
It has not been very long since the first book was published but
several things have been added to Cassandra and a few things have
changed. I am putting together a list of changed content,
Hi Edward,
Looking forward to your book. It's always interesting to read what others
have to say about a certain subject, and hopefully even learn new things!
2012/6/27 Raj N raj.cassan...@gmail.com
Great stuff!!!
On Tue, Jun 26, 2012 at 5:25 PM, Edward Capriolo edlinuxg...@gmail.comwrote:
Hey Edward,
I finally posted my (short) blog post on using Hector with Jruby:
http://synfin.net/sock_stream/technology/code/cassandra-hector-jruby-awesome
If you're interested in documenting that more in detail in your book,
let me know and I can help you with that in your book if you'd like.
Sounds good.
One thing I'd like to see is more coverage on Cassandra Internals. Out of
the box Cassandra's great but having a little inside knowledge can be very
useful because it helps you design your applications to work with
Cassandra; rather than having to later make endless optimizations that
On Wed, Jun 27, 2012 at 3:08 PM, Courtney Robinson court...@crlog.info wrote:
Sounds good.
One thing I'd like to see is more coverage on Cassandra Internals. Out of
the box Cassandra's great but having a little inside knowledge can be very
useful because it helps you design your applications
RE: API method signatures changing
That triggers another thought...
What terminology will you use in the book to describe the data model? CQL?
When we wrote the RefCard on
DZonehttp://refcardz.dzone.com/refcardz/apache-cassandra,
we intentionally favored/used CQL terminology. On advisement
On Wed, Jun 27, 2012 at 4:34 PM, Brian O'Neill b...@alumni.brown.edu wrote:
RE: API method signatures changing
That triggers another thought...
What terminology will you use in the book to describe the data model? CQL?
When we wrote the RefCard on DZone, we intentionally favored/used CQL
I'm looking forward to getting a few copies of this. Some areas that
would be great to cover
- Indexing strategies
- Configuring clients/env for sane timestamping
- Efficient CQL
- Top 8/10 perf issues/stacktraces and common resolutions
- understanding nodetool
Hi Edward,
That's a great news!
One thing I'd like to see in the new edition is Counters, known issues
and how to avoid them:
- avoid double counting (don't retry on failure, use write consistency
level ONE, use dedicated Hector connector?)
- delete counters (tricky, reset to zero?)
-
On Thu, Jun 28, 2012 at 7:32 AM, Edward Capriolo edlinuxg...@gmail.comwrote:
On Wed, Jun 27, 2012 at 4:34 PM, Brian O'Neill b...@alumni.brown.edu
wrote:
RE: API method signatures changing
That triggers another thought...
What terminology will you use in the book to describe the data
On Wed, Jun 27, 2012 at 1:34 PM, Brian O'Neill b...@alumni.brown.edu wrote:
RE: API method signatures changing
That triggers another thought...
What terminology will you use in the book to describe the data model? CQL?
When we wrote the RefCard on DZone, we intentionally favored/used CQL
13 matches
Mail list logo
