4 ms·
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-ela
by wiradikusuma 5y ago
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-vs-meilisearch/ https://typesense.org/typesense-vs-algolia-vs-elasticsearch-... (yes it's hosted by Typesense)
- victor106 5y agoHow do you handle stop words in Typesense?
- KaoruAoiShiho 5y agoAccording to the matrix it doesn't have support for it.
- marcinzm 5y agoYou could remove them from the query text yourself although since they'd still be in the index I suspect misspellings could cause issues.
- KaoruAoiShiho 5y agoDamn this matrix made me want to use Algolia.
- hitekker 5y agoSome 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/122 https://github.com/typesense/typesense/issues/95Oh 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 :/