Daniel Mewes

@pires Oh neat! I personally don't have a need for discovery, but I think some of the other readers of this thread might be interested. We should list it on...

(Opened https://github.com/rethinkdb/docs/issues/911 so we don't forget to put it in our docs)

Thanks for the suggestion @felixis-1 . I'm not sure if we are able to write and maintain the necessary integration at the moment, but we'll keep it as an open...

I like the idea. It's not the same as having native graph support in ReQL (https://github.com/rethinkdb/rethinkdb/issues/3142), but it would take away the burden of having to maintain a completely separate...

@deontologician not at the moment, but it might be a good idea to do so eventually.

Thanks for the suggestion @jcode89 . I'll put it on our list of integrations to look into. I'll see about how to prioritize this compared to some of the other...

@mlucy I suspect it would be a lot of work, and probably not worth it at the moment.

@frankleng We actually restructured the roadmap for the two upcoming releases slightly. The features this needs are now going to be in 2.2 (2.1 will instead have auto failover and...

I think this is a duplicate of https://github.com/rethinkdb/rethinkdb/issues/2732 @wojons, isn't it? Closing, but let me know if you think this one is different.

Ah I see. I think we will want to support a generic prioritization setting at some point. It would probably be accessible through the jobs table, so you could set...