Inconsistent "found" and "hits" values with object sorting
TLDR Michael is experiencing inconsistency between "found" and "hits" values when using object sorting. Kishore Nallan attributes the issue to a possible bug and asks for the dataset to investigate further.
May 17, 2023 (7 months ago)
Michael
12:21 PM
Kishore Nallan
01:18 PMMichael
01:38 PMMichael
01:38 PM/search?q=*&query_by=title,description&filter_by=attributes.make.name:[john-deere]&sort_by=created_at:desc&per_page=24&page=1Michael
01:39 PM{"facet_counts": [],"found": 43,"hits": [],"out_of": 1269,Michael
01:40 PMsearch?q=tractor&query_by=title,description&filter_by=attributes.make.name:[john-deere]&sort_by=created_at:desc&per_page=24&page=1I get both hits and found
{"facet_counts": [],"found": 2,"hits": [{"document": {"attributes": {Michael
01:41 PMsort: true the issue goes away, but I guess if that's there for the memory consumption reason, maybe I should structure my query differently?Kishore Nallan
02:32 PMKishore Nallan
02:33 PMfound is not zero.Michael
02:53 PMKishore Nallan
02:54 PMMichael
02:59 PM
Typesense
Indexed 3005 threads (79% resolved)
Similar Threads
Resolving Typesense Result Issue in Document Collection Queries
Mike was encountering errors when searching for specific query in their Typesense document collection. Jason suggested it may be due to the `drop_tokens_threshold` setting. There was a misunderstanding but after further explanation from Jason, Mike understood and decided to continue the conversation via email.
Querying with Typesense-Js and Handling Null Values
michtio was querying using typesense-js and receiving fewer results than expected. Kishore Nallan suggested using different query parameters. Further discussion led to the handling of 'null' values and filtering syntax in the search queries. The thread ended with Jason offering migration support from Algolia to Typesense.
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.
Improving System Performance and Typesense Query Efficiency
SamHendley was experiencing performance issues with Typesense's large-scale system testing and proposed several improvements. Both Jason and Kishore Nallan addressed the suggestions and corrected some misconceptions. They provided further clarification and recommended upgrades for better performance.
Issues Sorting Multiple Fields with Sort_by in Typesense Query
Rishabh was having trouble sorting two fields separately with a single query. Jason explained that a secondary sorting will only occur if the first sort results in matching values. They clarified the functionality of sorting in various search engines.