I had been following its development for a while, but then I moved to Typesense after evaluating this matrix:
https://typesense.org/typesense-vs-algolia-vs-elasticsearch-... (yes it's hosted by Typesense)
back
3 comments
Some basic features are missing from that doc. For example, typesense doesn’t handle periods, underscores, dashes and other characters as delimiters:
https://github.com/typesense/typesense/issues/122
https://github.com/typesense/typesense/issues/95Oh
The workaround they recommend is to duplicate your index with all those characters removed and then strip out those characters from your search queries :/
How do you handle stop words in Typesense?
You could remove them from the query text yourself although since they'd still be in the index I suspect misspellings could cause issues.
According to the matrix it doesn't have support for it.
Damn this matrix made me want to use Algolia.