It's so refreshing to see an open source project have the balls to announce a 1.0 early and not stay in the eternal "0.x we're still beta so don't blame us for any problems"-phase.<p>One thing that's stopping us from switching over is that we need more real world success stories of other people making the switch and being better off. For all its warts, Cassandra is the devil we know, but ScyllaDB is definitely something we're keeping an eye on.<p>One suggestion that might make it easier for people to move over is thorough testing of mixed clusters. I wouldn't mind switching one node in my cluster over, <i>if</i> I could be certain it wouldn't screw up the entire cluster. I saw that they ran through the Jepsen tests and did a good job, it would be very interesting to see how a 50/50 cassandra/scylladb cluster would fare in the same tests!
What's the status of secondary index? It was described as "half-ready" here[1]. Is that still the case?<p>Also does Scylla support some sort of data locality as far as secondary index is concerned?<p>For example if I want to store comments, I'd want to store all comments that belong to the same forum thread in a single node. All these comments have the same thread_id. Then I can have a secondary index on thread_id. When I want to get all comments that belong to a certain thread I can just query on the thread_id secondary index and only 1 node is queried. Is that possible?<p>[1] <a href="https://github.com/scylladb/scylla/issues/401" rel="nofollow">https://github.com/scylladb/scylla/issues/401</a>