#community-help

Stopword Support in Typesense Query

TLDR Ovid asked about stopword support in Typesense. Jason informed it's unprioritized but shared a client-side approach, and asked Ovid to open an issue on GitHub.

30mo

Join the chat

Mar 24, 2021 (30 months ago)

Photo of md5-5f10384cea2c36be049834fbb39fa553

Ovid

08:53 AM

I’ve noticed that there is no stopword support for Typesense, nor is there a ticket for it. I also can’t find a roadmap. Are stopwords planned?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

04:41 PM

We have an internal story for it and left it unprioritized until we had an ask from the community for it. Could you open an issue on GitHub?

04:42

Jason

04:42 PM

In the demo search apps I use a client-side stop words approach in the meantime

Ovid

06:03 PM

Jason Thank you. Here’s the issue. https://github.com/typesense/typesense/issues/248

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Typesense Stopwords Issue and Workaround

Narayan asked about Typesense issue #248 and its workaround. Kishore Nallan confirmed it's resolved in the development branch. Further questions about indexing and document scoring remain unanswered.

yesterday

Typesense Handling of Stop Words in Searches

Manuel asked if Typesense handles stop words. Jason replied that as of v0.25, users need to filter out stop words before querying, but v0.26 would add native support.

1mo

Typesense Cursor-Based Pagination Support

Raymond asks about cursor-based pagination in Typesense. Jason confirms it's not supported yet but links to a related GitHub issue. Kishore Nallan informs that the feature is available for testing.

6mo