Reputation
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
1 7 21
Newest
 Constituent
Impact
~225k people reached

Aug
4
answered cassandra in memory tables
Aug
4
awarded  Constituent
Jul
27
awarded  Caucus
Feb
2
revised What are the canonical NoSQL resources for people who never used this technology?
Removing dead link, and adding links to Cassandra resources.
Jan
23
comment Cassandra row ordering best practice
Cassandra can handle 2 billion columns in a row, so with articles 1000 per day and 3 cols per clustering key, you'll be storing 1.095 million columns per country each year. If that's not going to be enough, you could always make the articledate (like you were planning to, or even just part of it) part of the partitioning key, as well. Take a look at Pattern #2 in the Time Series article for more info on that.
Jan
23
answered Cassandra row ordering best practice
Jan
22
comment Upgrading Cassandra from 1.1.0 to latest
@TheSquad Not necessarily. You will be fine as long as you observe some general guidelines (no running repairs, no changing permissions, no using new features, etc).
Jan
21
answered Upgrading Cassandra from 1.1.0 to latest
Jan
8
awarded  Popular Question
Dec
1
awarded  Yearling
Nov
18
comment Do you have to run nodetool repair on every node?
@2rs2ts Yes, if you run it with -pr on every node it will cover the entire keyspace(s).
Nov
17
comment Date model for commenting system stored in a key-value NoSQL DB?
@AlbertLim For those UPDATEs, you should be able to encapsulate them with the BEGIN BATCH/APPLY BATCH statements. That will tell Cassandra to apply them as a single, logical operation. Check this SO answer for more info on that: stackoverflow.com/questions/26818576/…
Nov
14
answered Do you have to run nodetool repair on every node?
Nov
14
answered Date model for commenting system stored in a key-value NoSQL DB?
Nov
11
awarded  Revival
Nov
11
comment Cassandra: maintenance
@2rs2ts Well, not for "forever." Once you've run a manual compaction..."yes," you'll need to keep running it periodically (we would always do it right after our weekly repair). Clarify this with a DataStax rep, but I think that if you have an event that rewrites the SSTABLE files (like upgrading when you run upgradesstables) that may reset things enough to save you from "manual compaction hell."
Nov
4
comment Cassendra schema design suggestion for chat archive
+1 Brilliant answer!
Sep
23
answered Small startup: Cassandra + Hadoop or ElasticSearch
Sep
17
answered Keeping rows ordered by counter value
Aug
29
awarded  Notable Question