[continuations]

What's the status of secondary index? It was described as "half-ready" here[1]. Is that still the case?

Also does Scylla support some sort of data locality as far as secondary index is concerned?

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?

[1] https://github.com/scylladb/scylla/issues/401

[glommer]

We are starting developing our solution for secondary index right now. We haven't yet made a decision regarding how we'll implement it.

[continuations]

So a feature that was described as half-ready 7 months ago is actually still undecided design-wise 7 months later? That's surprising. When do you think secondary index will be available?

[glommer]

This feature was never described as half-ready. The ticket said we had half ready code, but it's part of the design process to choose whether or not we'll use that code. I can see, however, how this may give a reader the wrong impression, and I apologize for that.

As can be seen in the follow ups for that ticket, we haven't yet decided if we'll support standard secondary index, SASI, some form of materialized views, or all of them. Until we do, it's hard to commit to a timeline. Basic secondary index (for which we have code half ready) is pretty simple, and if we do implement it, it should land in our main version in a couple of weeks. The others are a bit more complicated.