jbellis

33 ms·

421.
by jbellis 13y ago
I was with you until the last sentence. Why would it be irresponsible to kill the Heroku also-ran to push faster on what people really want?
422.
by jbellis 13y ago
Yesterday's discussion: https://news.ycombinator.com/item?id=6542797
423.
by jbellis 13y ago
To answer my question, apparently the viewing angles are a lot more forgiving on the HP screen.
424.
by jbellis 13y ago
Is the difference between this and the $250 Samsung chromebook basically just the case? Same resolution, same amount of RAM, same tiny SSD.
425.
by jbellis 13y ago
Short answer: no. Longer answer: the only guarantee that's carved in stone is that in X.Y.Z is backwards-compatible for all values of Z. Past that YMMV, e.g., typically X.Y+1 will be network-compatible for rolling upgrades, but we&#x2
426.
by jbellis 13y ago
The principle is the same as with normal reads; expand the quorum to include both old and new owners until the transition is done: https://issues.apache.org/jira/browse/CASSANDRA-833?focusedC...
427.
by jbellis 13y ago
As I mentioned above, we fixed the bugs he ran into; this is not representative behavior of 2.0.1. The granularity is a CQL partition: http://www.datastax.com/documentation/cql/3.0/webhelp/index....
428.
by jbellis 13y ago
No excuses. It's as simple as me dropping the ball on this one.
429.
by jbellis 13y ago
I guess I'll have to settle for joining the crowd of incompetents behind PostgreSQL, Linux, the JVM, et al., who have also been known to release bug fixes on occasion. :)
430.
by jbellis 13y ago
It's awfully hard to prove a negative, but our test suites are open [1] [2], and so is our bug tracker [3]. [1] https://github.com/apache/cassandra/tree/trunk/test/unit/org... [2] https:&
431.
by jbellis 13y ago
It's important to distinguish architecture and design from implementation. The former may be correct, even if the latter is found to have a bug.
432.
by jbellis 13y ago
The bugs he ran into with lightweight transactions were fixed within days, two weeks ago, and included in the 2.0.1 release shortly afterwards.
433.
by jbellis 13y ago
That's the theory, anyway. http://homeschooling.penelopetrunk.com/2013/09/18/montessori...
434.
by jbellis 13y ago
1000 words on why this matters: http://www.slideshare.net/eonnen/high-performance-network-pr...
435.
by jbellis 13y ago
"We can easily see how to get linearizable consistency if we route all requests [for a partition or region] through a single master [like all the systems you listed]. In a fully distributed system, it is less obvious." Again, the
436.
by jbellis 13y ago
Hey, that's pretty cool. Thanks, and good luck to you too!
437.
by jbellis 13y ago
As I made clear [1], the novelty is in allowing opt-in to linearizability in a Dynamo-based system. To the best of my knowledge, Cassandra is indeed the first to offer this. The "lightweight" qualifier was carefully chosen to sug
438.
by jbellis 13y ago
Looks like the PSP re-release was Japan only. :(
439.
by jbellis 13y ago
http://en.wikipedia.org/wiki/Confirmation_bias
440.
by jbellis 13y ago
Just from the last couple weeks, Penny Arcade has published jokes about violence against children and torture: http://penny-arcade.com/comic/2013/08/19 http://penny-arcade.com/comic/2013&
441.
by jbellis 13y ago
Those of you who do not follow current events may not realize that this is not a straw man: http://www.christianpost.com/news/police-raid-home-seize-chi... (And those of you who are not parents do not fully comprehend
442.
by jbellis 13y ago
Homeschooled child of a college valedictorian and a Harvard PhD here to disagree with you.
443.
by jbellis 13y ago
Cassandra exposes functionality similar to checkAndPut as Lightweight Transactions: www.datastax.com/dev/blog/lightweight-transactions-in-cassandra-2-0
444.
by jbellis 13y ago
Good summary; thanks!
445.
by jbellis 13y ago
You're also giving up atomicity on writes when you actually do want to update multiple fields at once.
446.
by jbellis 13y ago
Correct. But, in that case vector clocks does not help you either [unless you are okay with both writers thinking they have "won" for an unbounded period of time]; what you really need is true linearizability: http://w
447.
by jbellis 13y ago
The whole point is that "conflicting" updates to a single column is supposed to cause overwrites ("data loss"). If I wanted to keep multiple values in a column around I'd use a Map or a Set instead! Maybe the dis
448.
by jbellis 13y ago
That is describing the 1072 approach aka the one in Cassandra today. Incrementing without read-before-write was one of the reasons Twitter liked it. Unfortunately, while you can increment on a single node without read-before-write, you n
449.
by jbellis 13y ago
I explained my reasoning in more detail in the paragraphs starting with "Vector clocks are good at helping clients with simple merges like the above user object, but it’s important to understand that vector clocks only tell you that a
450.
by jbellis 13y ago
If you want to manage opaque blobs then you should probably use Riak or Voldemort. Cassandra gives you a set of one-size-fits-most tools that by and large work very well together, but if you want more of a build-your-own-database toolkit,

More ›