#community-help

Querying Wildcards in a More Regex-y Way

TLDR Todd sought to use a more regex-like wildcard search. However, Jason clarified that only * or a keyword can be used due to performance issues.

19mo

Join the chat

Jun 14, 2022 (19 months ago)

Photo of md5-cccf0b87668408fef09dd77e1948fced

Todd

07:49 PM

With regard to the search stuff, I see we can supply a wildcard to indicate ‘match all strings’. Can we supply a wildcard in a more regex-y way?

I’d like to search something like prefix-*match*

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

07:53 PM

No unfortunately. It's just a * or a keyword

07:54

Jason

07:54 PM

Regex search is really hard to do in a performant way, because the list of strings it could match is infinite, and we'd essentially have to scan the whole dataset to find matches (which is similar to what LIKE %% does in SQL for eg)

Todd

08:01 PM

Absolutely. Thank you for explaining. I’ll keep trying to figure out how best to search our data.

Typesense

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

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Usage and Modification of Dynamic Routes in Typesense Documents

Ethan needed a way to perform exact queries through two fields in Typesense documents. Kishore Nallan demonstrated its possibility using the "filter_by". An issue was resolved via recommending that fields in 'query by' should be a string type.

11mo

Querying Documents Using Wildcards and Array Lengths

Orion asks about querying documents with wildcards or array lengths. Jason requests clarification and examples from Orion to better understand the question.

20mo

Phrase Search Relevancy and Weights Fix

Jan reported an issue with phrase search relevancy using Typesense Instantsearch Adapter. The problem occurred when searching phrases with double quotes. The team identified the issue to be related to weights and implemented a fix, improving the search results.

111

8mo