Re:RethinkDB 1.6 is out: regex matching, new array operation...
by coffeemug on Thursday June 13, 2013 @04:00PM
(#5876212)
Great question. In Rethink we guarantee that the document and its index entries are always in the same shard, so any change to the document that affects secondary indexes is consistent and atomic.
There are tradeoffs to this approach -- to read a secondary index the db has to go to every master/shard for the table, but there are lots of tricks we use to minimize the impact of this tradeoff.
Re:RethinkDB 1.6 is out: regex matching, new array operation...
by robert-zaremba on Sunday June 16, 2013 @02:50PM
(#5889426)
I will really love to see information about time complexity of DB operations
Re:RethinkDB 1.6 is out: regex matching, new array operation...
by coffeemug on Monday June 17, 2013 @09:42PM
(#5897068)
I'm actually working on this right now. We should get the updated api docs in about two weeks.
Re:RethinkDB 1.6 is out: regex matching, new array operation...
by andrewcooke on Thursday June 13, 2013 @09:32PM
(#5877805)
[apropos nothing, but since you're official, the linked page uses "unilaterally" in an odd way (to mean "uniformly"). imho. afaict. etc.]
Re:RethinkDB 1.6 is out: regex matching, new array operation...
by mglukhovsky on Thursday June 13, 2013 @11:54PM
(#5878173)
Great catch, we'll update the blog post!
It seems like it would be hard to guarantee that the document and its index entries are always in the same shard, and since RethinkDB doesn't seem to support general multi-document transactions, I'm curious how you go about updating them simultaneously.