we already have a field to save the "last modified time“, then in this case, how can I use _update API in crawling pipeline to make sure older version doc won't overwrite newer version doc?
The docs updated in CMS are async processed via a distributed messaging system (Azure event Hub, similar to Kafka) in our crawling pipeline, it is possible that the older doc might be processed and sending to ES index earlier than the newer doc.