3 ms·
We currently support range sharding by primary key. Both compression and custom sharding are things we definitely want to do (https://github.com/rethinkdb/reth
by danielmewes 12y ago
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 https://github.com/rethinkdb/rethinkdb/issues/1862 , possibly https://github.com/rethinkdb/rethinkdb/issues/364 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.
- ddorian43 12y agoThat means you'll REMOVE range-sharding right? I just thought that issue was already completed.
- danielmewes 12y agoUncertain. 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.