RethinkDB 2.0 is now production ready

Post by coffeemug » Tue, Apr 14, 2015, 11:51 PM UTC

exelius wrote: post #87

coffeemug wrote: post #62

Earlier quoted context omitted.

> No, the AGPL uses strong copyleft, so any future derivative work must be released under the same terms (and the same license or later versions if I'm not mistaken). The only possibility is to start a closed source clone that doesn't use any of the original code from zero. Slava @ RethinkDB here. This has one exception -- the copyright owner can choose to start releasing enhancements as closed source, and they would…

One caveat with this: if your project is open source and has accepted submissions from non-affiliated entities, you would either need to get them to assign the rights to that code to RethinkDB or remove them from the source if you were to relicense under something that would break the AGPL. This is where things like code releases come in. This is also why many open source startups don't accept code submissions from o…

Post by SamReidHughes » Wed, Apr 15, 2015, 12:20 AM UTC

lobster_johnson wrote: post #86

danielmewes wrote: post #78

Earlier quoted context omitted.

We did a couple of scalability improvements in 2.0, but didn't optimize groups and counts specifically. Would you mind writing me an email with your query or opening an issue at https://github.com/rethinkdb/rethinkdb/issues (unless you have already?)? I'd like to look into it to see how we can best improve this. We're planning to implemented a faster count algorithm that might help with this ( https://github.com/reth…

What I was doing is so trivial, you don't really need this information. This was my reference SQL query: select path, count(*) from posts group by path; (I don't have the exact Rethink query written down, but it was analogous to the SQL version.) You can demonstrate RethinkDB's performance issue with any largeish dataset by trying to group on a single field. The path column in this case has a cardinality of 94, and t…

Post by SamReidHughes » Wed, Apr 15, 2015, 1:06 AM UTC

lobster_johnson wrote: post #124

SamReidHughes wrote: post #123

Earlier quoted context omitted.

Are you sure the analogous RethinkDB query was using the index? Iirc it's not enough just to use the column name (or wasn't, I don't keep up).

It wasn't using an index, but then Postgres wasn't, either. I don't think aggregating via B-tree index is a good idea; aggregation is inherently suited to sequential access. An index is useful only when the selectivity is very low.

Post by jchrisa » Wed, Apr 15, 2015, 1:39 AM UTC

vogan42 wrote: post #112

jchrisa wrote: post #110

Earlier quoted context omitted.

Couchbase has indexing, map reduce, and full text. Also a mobile sync connector.

Couchbase conflict resolution is really basic, assuming you mean distributed in a wan context (eg xdcr). Riak would represent the state of the art in this respect (random internet endorsement, I'm not affiliated with anything, just a user who has worked with both systems).

Post by sterlingross » Wed, Apr 15, 2015, 2:14 AM UTC

geddski wrote: post #109

nileshtrivedi wrote: post #108

Earlier quoted context omitted.

Do you have any project on github that works like that?

Not that's open source, but I can do a little write up article and share a sample app that shows how to do it.