Partial Search on Phone Number Field in Database
TLDR Alan needed guidance to perform a partial search on a phone number field. Kishore Nallan explained that an infix search was required, this would drop and recreate the in-memory index without affecting the data. They advised executing it after hours to avoid interference with data being indexed and searches.
1
Oct 31, 2022 (14 months ago)
Alan
01:36 PMKishore Nallan
01:37 PMAlan
01:45 PMAlan
01:45 PMKishore Nallan
01:46 PMKishore Nallan
01:47 PMAlan
01:50 PMKishore Nallan
02:04 PMAlan
02:40 PMKishore Nallan
02:44 PMAlan
02:46 PM1
Alan
02:57 PMKishore Nallan
03:03 PMKishore Nallan
03:03 PMAlan
03:03 PMKishore Nallan
03:04 PMAlan
03:17 PMTypesense
Indexed 3015 threads (79% resolved)
Similar Threads
Searching Phone Number Issues in Typesense.
Robert was having issues searching phone numbers using Typesense. CaptainCodeman suggested storing the number as segments, while Jason clarified that Typesense only supports prefix queries and suggested workarounds.
Partial search filtering
Jason asked about partial match searching in Typesense similar to SQL's LIKE. Jason explained that Typesense has "prefix search" by default but "infix search" can be done by setting the search parameters.
Infix Search: Memory and CPU Intensity
Steffen inquired about the cost of infix search. Kishore Nallan explained that it is memory and CPU intensive, recommended for small fields or documents with less than 30K. You can switch it on/off at query time, but infix indexing must be enabled in the collection schema.
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.
Discussions on Typesense, Collections, and Dynamic Fields
Tugay shares plans to use Typesense for their SaaS platform and asks about collection sizes and sharding. Jason clarifies Typesense's capabilities and shares a beta feature. They discuss using unique collections per customer and new improvements. Kishore Nallan and Gabe comment on threading and data protection respectively.