jdf

7 ms·

31.
by jdf 14y ago
I had a TA at school who was blind and was excellent at helping CS students debug and fix their class projects. He helped me a number of times and was generally able to find bugs very quickly. While I don't know the name of the program of h
32.
by jdf 15y ago
What happens if a crash happens part way through the acknowledgement chain? For example, in your insert, if the node containing "x" crashes before it receives the ACK from the node containing "y" - do the dangling "y" and "z" insertions eve
33.
by jdf 15y ago
It looks like they trade the ability to scan ranges of keys for the ability to get single objects via multiple attributes. The value-dependent stuff is also a neat way of solving the consistency issues with multiple node updates. Interestin
34.
by jdf 15y ago
If you look up columnar databases, you can find a whole host of research on how these things store data. Storing values column by column to do vector processing is pretty common, but I can't recall seeing one built for a GPU before. Kudos t
35.
by jdf 15y ago
You can try out MapR's Hadoop distribution, which uses its own filesystem rather than HDFS. The MapR filesystem is not append-only, handles small files well, is easily accessible over NFS, etc. (*Note: I'm a MapR employee, so obviously I'll
36.
by jdf 15y ago
There are a number of other systems that allow this same approach of consistency and high availability. For example, Cassandra, which is freely available (as required by the poster), appears to be able to give you this behavior if you set C
37.
by jdf 16y ago
Similarly, I've been hoping that Rust (which is somewhat run by Mozilla labs folks) would turn out well: https://github.com/graydon/rust/wiki/
38.
by jdf 16y ago
> Yes, I did not mean that Megastore is eventually consistent. It is not, it's ACID compliant and uses Paxos. Real question: was this not stated clearly in my comment (I'd like to edit to clarify if it is)? I was interpreting the nod to
39.
by jdf 16y ago
The term "rows" could certainly be replaced with "tuples", "objects", or whatever else you prefer without changing any meaning of the post. If you look at the benchmarks posted on Mongo's site http://www.mongodb.org/display/DOCS/Benchmarks
40.
by jdf 16y ago
Eventual consistency often gives up the ability to develop applications against the system, because more reasoning about the state of the system has to be embedded in the application logic. For a better description of this problem, see this
41.
by jdf 16y ago
Looking at your first SELECT, there's very few RDBMSs on the market that won't evaluate that WHERE clause prior to the JOIN. (disclaimer: I work for Clustrix)