Understanding 'outOf' in Grouped Query and Documentation Issue
TLDR Bjarte shared a query with strange 'outOf' numbers, and discovered a documentation typo. Kishore Nallan explained the meaning of 'outOf', and they discussed filing an issue and considering convenience methods.
1
Mar 13, 2023 (9 months ago)
Bjarte
08:20 AMFetched challenge candidates info found=1809 page=1 outOf=180291
i am fetching page1 there are 1809 total hits and 180k pages? this is my query
params := &api.SearchCollectionParams{
Q: "*",
QueryBy: "owner",
FilterBy: StringPointer(fmt.Sprintf("number.play_id:%s", ids)),
IncludeFields: StringPointer("number.play_id,update_at,owner"),
GroupBy: StringPointer("owner"),
PerPage: IntegerPointer(250),
}
Bjarte
08:31 AMright now I am just doing the rest of the logic in golang, but doing it in lower layers is always better mechanical sympathy wise
Kishore Nallan
08:40 AMKishore Nallan
08:40 AMBjarte
08:41 AMBjarte
08:42 AMKishore Nallan
08:42 AMout_of
is total number of documents in the collection, and this is ungrouped count.Bjarte
08:43 AMBjarte
08:43 AMKishore Nallan
08:43 AMKishore Nallan
08:43 AMBjarte
08:43 AMKishore Nallan
08:43 AMBjarte
08:45 AMKishore Nallan
08:45 AMBjarte
09:01 AMBjarte
09:01 AMKishore Nallan
09:07 AMBjarte
09:07 AMBjarte
09:08 AMKishore Nallan
09:08 AMBjarte
09:09 AMBjarte
09:10 AMBjarte
09:10 AMBjarte
09:11 AMKishore Nallan
09:11 AMBjarte
09:11 AMBjarte
09:11 AM1
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
Typesense Bug Fix with `canceled_at` Field and Upgrade Concerns
Mateo reported an issue regarding the treatment of an optional field by Typesense which was confirmed a bug by Jason. After trying an upgrade, an error arose. Jason explained the bug was due to a recent change and proceeded to downgrade their version. Future upgrade protocols were discussed.
Integrating Semantic Search with Typesense
Krish wants to integrate a semantic search functionality with typesense but struggles with the limitations. Kishore Nallan provides resources, clarifications and workarounds to the raised issues.
Moving from Algolia to Typesense: Questions and Answers
Juan sought advice from Kishore Nallan about moving from Algolia to Typesense, handling MultiSearch, setting parameters, checking imported documents, and a specific syntax query.
Typesense Capabilities and Troubleshooting Queries
A had issues with refinement lists and analytics in Typesense. Jason provided a possible solution and recommended the analytics widget. They clarified import size limits and helped identify a filter issue in A's query. Upgrade options are in Typesense's roadmap.
Enhancing Vector Search Performance and Response Time using Multi-Search Feature
Bill faced performance issues with vector search using multi_search feature. Jason and Kishore Nallan suggested running models on a GPU and excluding large fields from the search. Through discussion, it was established that adding more CPUs and enabling server-side caching could enhance performance. The thread concluded with the user reaching a resolution.