Daniel Bimschas
07/02/2025, 12:11 PMFanis Tharropoulos
07/02/2025, 12:38 PMembed property's from prop. Since it's an array of strings, you can pass in any string field:
https://typesense.org/docs/29.0/api/vector-search.html#creating-an-auto-embedding-field
The embeddings will only be re-calculated when an embedding field changes, not when the document is changed, so there's o extra API call to your remote embedder thereDaniel Bimschas
07/08/2025, 4:17 AMDaniel Bimschas
07/08/2025, 6:01 AMFanis Tharropoulos
07/09/2025, 9:48 AMDaniel Bimschas
07/10/2025, 8:54 AMLastly, could you describe what part of the documentation based on caching is not up to par? We strive for a fully documented API and feedback is always welcomeAt this point I feel the documentation on caching is quite hidden (could only find it in https://typesense.org/docs/29.0/api/server-configuration.html#resource-usage). Iād expect itās own section somewhere in the vicinity of https://typesense.org/docs/29.0/api/vector-search.html#index-embeddings. Furthermore, I think it should explain in more detail how the caching behaves exactly. Technically speaking, e.g. the question on my mind is: how is the caching key constructed / which input goes in? Does it hash only the document contents or does it also include e.g. the chosen model and any parameters going into the embedding generation? Under which conditions will the embedding be recalculated, when will it be taken from the cache? Is the cache persistent and thereby survives server restarts? Is the cache distributed and therefore works in a clustered scenario? Some one of these questions are going beyond what I need, but these are examples of questions that come to my mind when I read about a caching feature. I could look at the implementation to get answers, but the implementation might just be a snapshot and the behaviour might change without me noticing. Documentation typically serves more as a āspecificationā, describing how things should work.
Daniel Bimschas
07/10/2025, 8:55 AMIs LiteLLM OpenAI compatible? From a quick read, I saw that it standardizes the API format, but is it hosted on a remote URL like we describe in the docs?
Daniel Bimschas
07/10/2025, 8:56 AMFanis Tharropoulos
07/10/2025, 9:46 AMAt this point I feel the documentation on caching is quite hidden (could only find it in https://typesense.org/docs/29.0/api/server-configuration.html#resource-usage). Iād expect itās own section somewhere in the vicinity of https://typesense.org/docs/29.0/api/vector-search.html#index-embeddings.
Furthermore, I think it should explain in more detail how the caching behaves exactly.
Technically speaking, e.g. the question on my mind is: how is the caching key constructed / which input goes in? Does it hash only the document contents or does it also include e.g. the chosen model and any parameters going into the embedding generation? Under which conditions will the embedding be recalculated, when will it be taken from the cache? Is the cache persistent and thereby survives server restarts? Is the cache distributed and therefore works in a clustered scenario?
Some one of these questions are going beyond what I need, but these are examples of questions that come to my mind when I read about a caching feature. I could look at the implementation to get answers, but the implementation might just be a snapshot and the behaviour might change without me noticing. Documentation typically serves more as a āspecificationā, describing how things should work.We'll definitely add mention of it under the vector search docs, and we'll try to cover some technical aspects of the implementation, but we're trying to keep documentation readable for new-comers as well, so we may not go into full detail. Thanks for the feedback!