undefined | Better HN

0 pointsdanielmewes11y ago0 comments

We currently support range sharding by primary key.

Both compression and custom sharding are things we definitely want to do (https://github.com/rethinkdb/rethinkdb/issues/1862 , possibly https://github.com/rethinkdb/rethinkdb/issues/364).

I can't give an ETA on these features yet, but it will probably happen later this year.

0 comments

2 comments · 1 top-level

ddorian4311y ago· 1 in thread

That means you'll REMOVE range-sharding right? I just thought that issue was already completed.

danielmewesOP11y ago

Uncertain. The issue is still in the planning phase. We'll only remove range sharding if we're confident that hash-based sharding provides an adequate replacement of course. It's possible we'll keep both.

j / k navigate · click thread line to collapse