Ingest timestamp

Is it possible for ingest timestamp (introduced via ingest pipeline) to be out of order with respect to actual index time (when a document becomes queryable)


doc_1 => ingest_time_t1
doc_2 => ingest_time_t2
ingest_time_t1 > ingest_time_t2

but search query returns t1 first (since that document gets indexed first)

The use case is to periodically read data from elastic search and do checkpointing regarding what data has been already read. Is it possible to solve this by introducing ingest timestamp, and using it for checkpointing?

I suspect this will depend on how many primary shards the index have. Refreshes are not coordinated across primary shards in an index so it is possible that a later time stamp becomes searchable before an earlier one if they are on different primary shards.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.