# Documents with date (epoch\_millis) sent in bursts and not in time-increasing order are indexed stragely **URL:** \ **Category:** Elasticsearch\ **Created:** [July 31, 2020, 9:55am UTC](https://discuss.elastic.co/t/documents-with-date-epoch-millis-sent-in-bursts-and-not-in-time-increasing-order-are-indexed-stragely/243332 "2020-07-31T09:55:32Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mujina93](https://avatars.discourse-cdn.com/v4/letter/m/dfb087/32.png) [@mujina93](https://discuss.elastic.co/u/mujina93)\ **Post date:** [July 31, 2020, 9:55am UTC](https://discuss.elastic.co/t/documents-with-date-epoch-millis-sent-in-bursts-and-not-in-time-increasing-order-are-indexed-stragely/243332/1 "2020-07-31T09:55:32Z")
Does elasticsearch expect the date field to be in increasing order? I am sending docs from python using elasticsearch-py. The documents I send are sent in bursts (think sending some documents every random interval, like on average 100 documents every second), and I'm using the `index` api to tell elasticsearch to index each one of them (I'm using `index` and not `create` because I want an automatically created ID). These documents have a date field (in `epoch_millis`). The point is: the dates are increasing within a burst, but they aren't across different bursts. For example. I may send now a burst of 10 documents, whose dates are 1000000000011, 1000000000012, ..., 1000000000020 (imagine these are increasing epoch\_millis that make sense). Then, in 1 second, I send another burst whose dates are like: 1000000000001, 1000000000002, ... etc. (Elasticsearch receives **after** documents whose date are **before** dates that it has already received and indexed. My problem is that these documents are indexed very strangely. They end up being lumped quite at random. Sometimes they have the right date, sometimes they are indexed all at some wrong time bin, sometimes I don't get any document in elasticsearch for time ranges in which I should see documents. I'm not sure if the problem is caused by something related to how elasticsearch indexes documents by dates, or by some obscure problem of elasticsearch-py, or by some other low-level issue like network clogging. I wouldn't know. To me it just seems that elasticsearch is "making confusion" in indexing all these documents. Note: if I send one document alone (for example via curl), it is indexed correctly. ---
**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\ **Post date:** [August 2, 2020, 1:36am UTC](https://discuss.elastic.co/t/documents-with-date-epoch-millis-sent-in-bursts-and-not-in-time-increasing-order-are-indexed-stragely/243332/2 "2020-08-02T01:36:04Z")
Do you mean @timestamp? Are you mapping your date field to @timestamp? ---
**Author:** ![mujina93](https://avatars.discourse-cdn.com/v4/letter/m/dfb087/32.png) [@mujina93](https://discuss.elastic.co/u/mujina93)\ **Post date:** [August 3, 2020, 7:47am UTC](https://discuss.elastic.co/t/documents-with-date-epoch-millis-sent-in-bursts-and-not-in-time-increasing-order-are-indexed-stragely/243332/3 "2020-08-03T07:47:56Z")
My field is called `tsEvent`, it's of type `date`, format `epoch_millis`. I'm on Elasticsearch 7.7. The mapping of my index has a predefined schema, `"dynamic": "strict"`, date and numeric detection disabled, source enabled (if I disable it nothing seem to get stored and I can't see anything from kibana), routing set to false. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 31, 2020, 7:47am UTC](https://discuss.elastic.co/t/documents-with-date-epoch-millis-sent-in-bursts-and-not-in-time-increasing-order-are-indexed-stragely/243332/4 "2020-08-31T07:47:57Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.