- Merging content and index clusters to one to make index clusters elastic and auto-recovering on data loss.
- Fully realtime writes.
- Support more advanced machine-learned ranking through tensors.
- Streaming (personal) search supporting a large write rate.
- Document references.
- WAND and RANK operators.
- Rank features over multivalue text fields.
- Predicate fields.
- Lots and lots of performance work.
If you have dynamic fields like in your SaaS example I recommend using a single map field rather than let data not under your control drive changes to the set of fields.
> Do you know how long a package update takes in Vespa, to add, say, a single field?
A few seconds. However, rather than having operators do any of this manually, set up an automatic process which deploys on each change made to the repo (i.e do CD).
> all the reference documentation in one place
https://docs.vespa.ai/documentation/api.html