Originally from the User Slack
@Mosca_Careca: Is full text search supported in scyllaDB or is a secondary service like ElasticSearch still needed?
@Felipe_Cardeneti_Mendes: You can probably mimic it if the query in question always specify the partition key, but if it doesn’t then a secondary service is the way to go
@scyllero: @Felipe_Cardeneti_Mendes and how would you handle that? Let say you have a chat app: you write the message to Scylla first, and then to elastic . Ok, but how do you do that reliably?
@Felipe_Cardeneti_Mendes: If you are using ScyllaDB as your source of truth, in that case you would deltas via CDC. https://github.com/scylladb/scylla-cdc-source-connector/blob/master/QUICKSTART-ELASTICSEARCH-INTEGRATION.md
GitHub: scylla-cdc-source-connector/QUICKSTART-ELASTICSEARCH-INTEGRATION.md at master · scylladb/scylla-cdc-source-connector
@Mosca_Careca: Does ScyllaDB even have any type of Keyword-based search over text fields? Let’s say I want my users to be able to give me a query so that I can retrieve products whose description fits that query. Am I just forced to use a secondary service or is there any other way of solving this problem? Technically I could have a description_tokens table and implement my own full-text search, but I’d rather not reinvent the wheel here 
@scyllero: Go for a secondary service. Do not waste your time. Refer to that last reply from @Felipe_Cardeneti_Mendes
The flow would be
your app emitting products - scylladb - cdc source connector - kafka - sink connector (or custom consumer) - mongodb (if text queries are simple) or elasticsearch
@Mosca_Careca: Yeah sadly, that’ll have to be done. I feel like that many things running on my machine will nuke it, but we’ll see.