# Are hashes/objects saved in order?

**URL:** <https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881>\
**Category:** Elasticsearch\
**Created:** [August 5, 2020, 2:42pm UTC](https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881 "2020-08-05T14:42:51Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![spdoes](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@spdoes](https://discuss.elastic.co/u/spdoes)\
**Post date:** [August 5, 2020, 2:42pm UTC](https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881/1 "2020-08-05T14:42:52Z")

</div>

if I insert this field in this order:  
`"name_of_field": {"first":1,"second":2,"third":3}`

will it always save in the same order as I inserted ?

Based on my test, inserting multiple objects like that can make it save it different order, like:

`"name_of_field": {"third":3,"first":1,"second":2}`

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 5, 2020, 3:23pm UTC](https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881/2 "2020-08-05T15:23:26Z")

</div>

Elasticsearch does not change the document but JSON serialisation and deserialisation does generally not guarantee that order is preserved.

---

<div class="post-metadata">

**Author:** ![spdoes](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@spdoes](https://discuss.elastic.co/u/spdoes)\
**Post date:** [August 5, 2020, 4:10pm UTC](https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881/3 "2020-08-05T16:10:18Z")

</div>

Is there any way I could enforce an order on a particular hash field ?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 5, 2020, 4:16pm UTC](https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881/4 "2020-08-05T16:16:20Z")

</div>

To do so you would need to control how your documents are serialised and deserialised which means e.g. not using scripted updates. Which client(s) are you using?

---

<div class="post-metadata">

**Author:** ![spdoes](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@spdoes](https://discuss.elastic.co/u/spdoes)\
**Post date:** [August 5, 2020, 4:21pm UTC](https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881/5 "2020-08-05T16:21:43Z")

</div>

Ruby Elasticsearch gem: [https://github.com/elastic/elasticsearch-ruby](https://github.com/elastic/elasticsearch-ruby)

Do you want me to send the update query here ?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 5, 2020, 4:22pm UTC](https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881/6 "2020-08-05T16:22:42Z")

</div>

I will update recommended not relying on the order as it will be more resilient given that ordering is generally not guaranteed.

---

<div class="post-metadata">

**Author:** ![spdoes](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@spdoes](https://discuss.elastic.co/u/spdoes)\
**Post date:** [August 5, 2020, 4:25pm UTC](https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881/7 "2020-08-05T16:25:30Z")

</div>

Alright then,  
so the best will probably be to put it under an array, like:

`"name_of_field": [{"first":1},{"second":2},{"third":3}]`

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 5, 2020, 4:28pm UTC](https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881/8 "2020-08-05T16:28:35Z")

</div>

That sounds like a bad idea. Why do you feel you need to preserve order??

---

<div class="post-metadata">

**Author:** ![spdoes](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@spdoes](https://discuss.elastic.co/u/spdoes)\
**Post date:** [August 5, 2020, 4:44pm UTC](https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881/9 "2020-08-05T16:44:37Z")

</div>

This object will be sent through an API that will send to the browser and it needs to be displayed in a certain order

---

<div class="post-metadata">

**Author:** ![spdoes](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@spdoes](https://discuss.elastic.co/u/spdoes)\
**Post date:** [August 5, 2020, 5:30pm UTC](https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881/10 "2020-08-05T17:30:13Z")

</div>

any suggestion on a better way to deal with this ?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 5, 2020, 5:33pm UTC](https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881/11 "2020-08-05T17:33:15Z")

</div>

Sort it in the browser?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 2, 2020, 5:33pm UTC](https://discuss.elastic.co/t/are-hashes-objects-saved-in-order/243881/12 "2020-09-02T17:33:18Z")

</div>

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