#community-help

Retrieving Multiple Documents by ID in Typesense

TLDR Bruno asked about retrieving multiple documents by ID in Typesense. Jason suggested using filter_by: id:= and gave advice on POST requests and order preservation. Bruno successfully implemented these solutions.

5mo

Join the chat

Jun 15, 2023 (6 months ago)

Photo of md5-d9ca032e3941589aafa8433269974f96

Bruno

10:38 PM

Quick question, not sure if I missed it: is there a way to retrieve multiple documents by ID in one request? Use case is that we run a ~90k document lunr index in the user's browser, so that search feels instant even when connection is crap, but that only holds title and ID for obvious resource contraint reasons, and we'd love to in a second step then augment those results by fetching the remaining data out of Typesense.

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

10:39 PM

Yup, you can do filter_by: id:=[1,2,3]

Bruno

10:41 PM

Perfect!

10:45

Bruno

10:45 PM

It's a special extra layer for one of 4 indices, the other ones already work like a charm directly out of Typesense, where federated hums with lots of data and vector searches are doing exactly what they should, really solid job!

Jason

10:46 PM

That’s great to hear! 🙏

Jul 03, 2023 (5 months ago)

Bruno

07:51 PM

Uhm, stupid question Jason re fetching a set of docs as per above: is there a way to POST a simple search (JSON \q:'*', filter...) in a collection or do I always need to build a GET request string?

07:52

Bruno

07:52 PM

Tried posting to <http://localhost:8108/collections/foo/documents/search>

07:52

Bruno

07:52 PM

Which 404s

Jason

07:53 PM

You can send a POST with a JSON structure to the multi_search endpoint even it’s just a single search

Bruno

07:54 PM

Got it, thats the one we're using so far - performance should be the same?

Jason

07:54 PM

Yup

Bruno

07:57 PM

Thanks a lot as always!

08:15

Bruno

08:15 PM

Quick follow up: works, but the results have a different order than the array of IDs we filtered by - is there a way to preserve it?

Jason

08:15 PM

Filtering is not order-preserving… You would have to use the sort_by parameter to preserve order, or alternatively use the pinned_hits search parameter

Bruno

08:20 PM

Got it, its a short list with no predictable order we can pass to typesense sort_by so think sorting it in the client makes most sense.

08:30

Bruno

08:30 PM

Darn, its such a pleasure working with Typesense, it's when youre not sure and the give it a shot anyway and it just works flawlessly...

08:30

Bruno

08:30 PM

DId this.current.results.plants.items.map(function(el,i){order += el.id + ':' + (i+1) + ',';buffer.push(parseInt(el.id))})

08:30

Bruno

08:30 PM

and used pinned and works like a charm, thank you!

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Multiple Filters and JSON Requests in Typesense

Manish asked about multiple filter_by arguments, JSON input, and using multisearch. Jason offered typesense documentation links, examples, and how to use JSON formatted requests with multisearch. Ed shared a similar use case.

5mo

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.

11mo

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.

22mo

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.

26mo

Querying with Not-in in Typesense

Masahiro inquired about using not-in queries in Typesense. Kishore Nallan explained how to conduct such queries by using the "-" operator in the query string, and assisted Masahiro with issues stemming from a high number of exclusion tokens. The problem was eventually resolved by switching to the `multi_search` endpoint.

34mo