# Map.merge doesn't work with nested maps \[Resolved\]

**URL:** <https://discuss.aerospike.com/t/map-merge-doesnt-work-with-nested-maps-resolved/1907>\
**Category:** Python Client\
**Created:** [September 25, 2015, 1:51pm UTC](https://discuss.aerospike.com/t/map-merge-doesnt-work-with-nested-maps-resolved/1907 "2015-09-25T13:51:07Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![rbotzer](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/rbotzer/32/2114_2.png) [@rbotzer](https://discuss.aerospike.com/u/rbotzer)\
**Post date:** [November 7, 2019, 5:05pm UTC](https://discuss.aerospike.com/t/map-merge-doesnt-work-with-nested-maps-resolved/1907/15 "2019-11-07T17:05:47Z")

</div>

See

> [@Nested map read/get API](https://discuss.aerospike.com/t/nested-map-read-get-api/4030/2):
>
> As of [Aerospike version 4.6](https://www.aerospike.com/blog/aerospike-4-6-enhancing-security-developer-features/) you can apply [list](https://www.aerospike.com/docs/guide/cdt-list.html) and [map](https://www.aerospike.com/docs/guide/cdt-map.html) operations on nested structures at arbitrary depths by defining a [context](https://www.aerospike.com/docs/guide/cdt-context.html). The context is the logical/physical path to finding the nested element you want to operate on. I wrote a medium post on the topic

---

_[View the full topic](https://discuss.aerospike.com/t/map-merge-doesnt-work-with-nested-maps-resolved/1907)._