Hey. Does Typesense support some kind of optimistic concurrency control like Elasticsearch does?

We do maintain sequence numbers internally to serialize all writes and replicate them to the other nodes in the clusters, but we don't expose this in the API. Could you elaborate on what you're trying to accomplish?

We were evaluating Typesense as an alternative to Elasticsearch for storing our CQRS-style read models, and since our architecture is such that a given read model document might be attempted to be updated concurrently, we need a mechanism (like Elasticsearch's `seq_num`+`primary_term` stuff — see docs) for optimistic locking. Effectively a conditional update feature would also do the trick; something like an SQL

UPDATE Table SET Column=Value WHERE Id = '...' AND Version = 24

.

I've seen users using last updated at timestamps for this, in place of version numbers for this purpose

Not sure how timestamps would make a different given that there's no conditional update functionality in Typesense; could you give me a quick example?

There is a conditional update endpoint: https://typesense.org/docs/27.1/api/documents.html#update-by-query