Scylla: collection indexing issue (bug)

[LouayKamel]

• [] I have read the disclaimer above, and I am reporting a suspected malfunction in Scylla.

Installation details
Scylla version (or git commit hash): 2.3 AUG 26
Cluster size: 1 development node
OS (RHEL/CentOS/Ubuntu/AWS AMI): FEDORA 28

it seems there is a bug in Scylla secondary index,
I created an INDEX on map column, and then when I try to select by a key or value or even entire map it gave me an NoHostAvailable: and then the whole scylla stop working and had to restart it.. I tried all the options with no matter how I create the index( entires, keys, values, full).
then I tried it on ubuntu 18.04 and it didn't gave me any error or result just the whole system got frozen within a min due to memory leaks or cpu heavy load,

what should I do? I am designing a data model for a graph library and this is so important,
is there any plans to support map indexing by materialized views?

Thank you

[tzach]

@duarten ?

[nyh]

Lack of support for indexing a collection column is unfortunately a known issue, this is a duplicate of #2962.
I wasn't aware until now that it causes a crash if attempted.

[duarten]

We should at least fail gracefully if users try to index a non-frozen collection, instead of crashing randomly.

[LouayKamel]

Whats about the secondary custom index (SASI) ? in Cassandra there is multi modes(PREFIX, CONTAIN, SPARSE) which provide full text searching for index column, is there any plans to support this feature as well? example,
for now we can't create secondary indexes on top of partition key or MV, is this going to change in future?

[duarten]

We don't have plans to support SASI in the short term.

Indexes can't be built on top of MV (because indexes are MVs), but it should be possible to index any partition key column.

[duarten]

https://github.com/scylladb/scylla/commit/2d355bdf47b49820ef1c235ce3254fc15b5a354d fixed the crash and both #3654 and #2962 are being used to track support for indexing collections.