Discussing Solr's `stored=true` Field Property and Typesense Functionality
TLDR James inquired about a Typesense equivalent for Solr's stored=true
field property. Kishore Nallan clarified that Typesense stores all document fields. CaptainCodeman elaborated on scenarios for storing data, especially data that wouldn't be queried often.
Sep 14, 2021 (26 months ago)
James
04:11 PMstored=true
where the field name can be a query param?Kishore Nallan
04:12 PMJames
04:17 PMstored=true
vs indexed=true
paramsCaptainCodeman
04:26 PMJames
07:23 PMbrand_img_url
would be the query while the value would be the result. Not necessarily searching through the value itself. (I hope I'm understanding CaptainCodeman’s example properly)CaptainCodeman
07:36 PMTypesense
Indexed 2779 threads (79% resolved)
Similar Threads
Discussing Data Retrieval in Typesense Cloud Tool
Ricardo inquired about the impact of using non-searched fields in data records with Typesense. Jason explained that all fields are fetched from the disk, even if unindexed, pointing out it might not affect performance, with the benefit of reducing separate database API calls.
Solving Typesense Cloud Interface Issue in Python
Orion had an issue querying from Python in the Typesense Cloud interface. Kishore Nallan identified the problem within the array declaration. They then discussed improving error messages and Orion offered to make a PR.
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.