#community-help

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.

Powered by Struct AI
6
26mo
Solved
Join the chat
Sep 14, 2021 (26 months ago)
James
Photo of md5-ae7223c767d7228418baf97773be94d6
James
04:11 PM
Hello. Is there a field property like Solr's stored=true where the field name can be a query param?
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
04:12 PM
👋 All fields in a document are stored in Typesense. So the entire document is fetched in the search results by default.
James
Photo of md5-ae7223c767d7228418baf97773be94d6
James
04:17 PM
Ok, thank you. I'll go back to my data team and see if we're actually making use of this Solr stored=true vs indexed=true params
CaptainCodeman
Photo of md5-d3a4ca49ba4aeb3b9d0cb7d846eb0989
CaptainCodeman
04:26 PM
it makes sense to store things you may never query - for example an image URL to display in search results. Otherwise you’d have to be looking those up in some other database to render the results
James
Photo of md5-ae7223c767d7228418baf97773be94d6
James
07:23 PM
I think the URL example is actually great. I might not want to query the field value, but get the value by querying the field name. So the field name brand_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
Photo of md5-d3a4ca49ba4aeb3b9d0cb7d846eb0989
CaptainCodeman
07:36 PM
the URL would be the value, it’s unlikely to be something you’d ever query for itself (not sure you can say “don’t bother indexing this”) but you want it in the results to display so it needs to be stored in the doc to save looking it up elsewhere