#community-help

Partial Word Search in Datasets

TLDR Tatu inquired about partial word search in datasets. Kishore Nallan and Jason proposed solutions, with Tatu later submitting a GitHub issue for tracking.

24mo

Join the chat

Sep 28, 2021 (24 months ago)

Photo of md5-b4a54d591f9148a83dc5f8e2fed6f871

Tatu

02:16 PM

Is there currently any way to search for partial matches in words? Eg. a product with code 157B2210 should be findable with query B2210, but currently that doesn't seem possible as only prefix queries are supported?

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

02:19 PM

We've just had a couple of other customers ask for this feature. This requires suffix searching, which is not an easy problem to solve. It requires building a suffix tree, which is really complex and requires a high memory foot print or requires just doing a fast brute force search on the strings. It's a memory vs speed trade off.

How big is your dataset?

Tatu

02:31 PM

Around 300k records, using ~700MB of memory

02:34

Tatu

02:34 PM

Perhaps a possible brute force search could be enabled on a field by field basis? For example when searching through product codes, the strings are short and probably quickly searchable.

Kishore Nallan

02:39 PM

Yes that should be doable.

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

03:14 PM

One workaround in the meantime is to split each character combination into an array field and search on that.

05:50

Jason

05:50 PM

Tatu Mind creating a github issue for this, so we can track it?

Tatu

10:51 PM

https://github.com/typesense/typesense/issues/393

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 Infix Search for Partial Word Matching

Eric needed help with Typesense infix search for partial word matching. Kishore Nallan advised to enable it through infix: true in the collection schema.

6mo

Resolving Short Word Precedence Issue in Typesense Search

Jake experienced partial short word matches in a typesense search taking precedence over exact matches. Kishore Nallan recommended adjusting the query order, using 'exhaustive_search', and setting 'max_candidates' to optimize results.

2mo

Understanding Typesense Facets Search Functionality

Luke asked about facets search. Kishore Nallan explained that Typesense supports type ahead/interactive searching. Bruno figured out they mistook partial word search for within words search.

26mo

Adjusting Text Match Score Calculation in TypeSense

Johannes wanted to modify the Text Match Score calculation in TypeSense to improve search results returns. With counsel from Jason and Kishore Nallan, various solutions were proposed, including creating a Github issue, attempting different parameters, and updating Docker to a new version to resolve the matter.

15mo

Resolving Typesense Search Issues

Conversation started by Maximilian about Typesense search behavior led to Users Kishore Nallan and Mike discussing and suggesting workaround, with Kishore Nallan promising an official solution soon. No final confirmation of resolution provided.

17mo