sequence.concatMap(mappingFunction) -> stream
array.concatMap(mappingFunction) -> array
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After spending the better part of the month implementing date support | |
in RethinkDB, Mike Lucy sent the team the following e-mail. It would | |
have been funny, if it didn't cause thousands of programmers so much | |
pain. Read it, laugh, and weep! | |
----- | |
So, it turns out that we're only going to support dates between the | |
year 1400 and the year 10000 (inclusive), because that's what boost | |
supports. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
git log --pretty=format:"%H|%ae|%at|%s" | \ | |
python -c " \ | |
import rethinkdb as r; \ | |
import sys; \ | |
r.connect().repl(); \ | |
r.table_create('commits').run(); \ | |
r.table('commits').insert([dict(map(lambda x, y: [x, y], \ | |
['id', 'email', 'date', 'subject'], \ | |
line.split('|', 3))) \ | |
for line in sys.stdin]) \ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
"""Compares rethinkdb with mongo. Copied from http://pastebin.com/3PqdFTjc. Example output: | |
mongodb: 0.110867023468 | |
rethink: 2.25043606758 | |
""" | |
import copy | |
import pymongo | |
import rethinkdb as r | |
import time |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
David, sorry you ran into these issues. The crash is a known bug, and will be fixed in the 1.12 release (along with the new cache implementation). See https://github.com/rethinkdb/rethinkdb/issues/1389 for more details. | |
As to the performance you're getting, could you give some additional info so we could track this down? | |
- Which OS/version are you running? | |
- Which RethinkDB version are you running? (you can tell by running `rethinkdb --version`) | |
- Which client driver are you using (and which version)? | |
- What query do you use to get out 100 documents and how are you measuing latency? | |
Would really appreciate your feedback so we could fix these issues. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
r.table('authors').filter(lambda author: | |
r.table('users')['last_name'].contains(author['last_name'])). | |
run(conn) |
There are a number of breaking changes in RethinkDB 1.12 you should be aware of before migrating.
First, make sure to go through the regular data migration process, since the 1.12 file format isn't compatible with file formats generated by previous versions of RethinkDB.
Then, replace group_by
and grouped_map_reduce
commands in your applications with the new group
command.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
r.http("https://hacker-news.firebaseio.com/v0/topstories.json").limit(5).map( | |
r.http(r.add("https://hacker-news.firebaseio.com/v0/item/", | |
r.row.coerceTo('string'), | |
".json")) | |
); |
I hereby claim:
- I am coffeemug on github.
- I am coffeemug (https://keybase.io/coffeemug) on keybase.
- I have a public key whose fingerprint is 5925 55F9 CC4C 2D4E E82E 97AA A33E 7D8E 5279 41E9
To claim this, I am signing this object:
- Inexplicable perversity of human nature.
- The clever machinations of MongoDB's marketing people.
- The AGPL license killed it.
- We spent too long development before monetizing.
- Bad performance.
- Numeric types limited to a 64-bit `float`.
- Great product, but didn't/couldn't translate to revenue.
- Bad business model.
- Failure in timezones/timestamp nuances.