Resolving Search Parameter Issues in Endpoint
TLDR Julian had issues with endpoint search parameters not returning expected results. Jason and Kishore Nallan suggested using exhaustive_search=true
and max_candidates=1000
respectively, which resolved the issue.

Jan 26, 2023 (8 months ago)
Julian
11:00 PMWhat do you recommend me to check in this case? When the search term is zp9Sis, I’m expecting to match with strings like zp9Sis-230123-001, zp9Sis-230123-011 and zp9Sis-230123-021 (the last three are a serial number). But, currently only some of them appear (10), except when the search is more precise, like zp9Sis-230123-00. I’m hitting this endpoint with these URL params:
query_by=confirmation_id,purchase_order_identifiers&num_typos=0&sort_by=&highlight_full_fields=confirmation_id,purchase_order_identifiers&q=zp9Sis-230123-&facet_by=arrival_time,facility_name,checkin_status,scheduler_name,equipment_type_id,status,appointment_type_name,created_by_name&filter_by=&max_facet_values=10&page=1&per_page=25
I even added the - to the symbols_to_index search param. Thanks in advance.
Jason
11:02 PMexhaustive_search=true
as a search parameter and try again?Jan 27, 2023 (8 months ago)
Julian
03:24 AM
Kishore Nallan
06:15 AMmax_candidates
param. This directly controls the number of unique words to be used as candidates for search when there are multiple words that share the same prefix. Set this to a higher value like 1000
. The exhaustive_search
can be more expensive because it increases a bunch of other limits including max_candidates
and you probably don't need that here.Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
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.


Fixing Multiple Document Retrieval in Typesense
Phil needed an efficient way to retrieve multiple documents by id. Kishore Nallan proposed a solution available in a pre-release build. After some bug fixing regarding id matching by Jason and Kishore Nallan, Phil successfully tested the solution.



Querying and Indexing Multiple Elements Issues
Krish queried fields with multiple elements, which Kishore Nallan suggested checking `drop_tokens_threshold`. Krish wished to force OR mode for token, but Kishore Nallan admitted the feature was missing. Krish was able to resolve the issue with url encoding.