Implementing a lock in Elasticsearch
At Kestra, the workflow orchestration and scheduling platform I work for, we have two repository implementations: JDBC (with support for H2, MySQL, and Postgres) and Elasticsearch. In JDBC, locking a record for processing is fairly easy: SELECT FOR UPDATE … WHERE … will place a lock on the record(s) We process the record(s) in the same transaction UPDATE… At the end of the transaction, the database will automatically release the locks obtained via SELECT FOR UPDATE. But Elasticsearch does not…