{"push_id":1015822044,"size":1,"distinct_size":1,"ref":"refs/heads/dynamic_mappers_are_hard","head":"96ec48afcde8b8689cbce09e6f8afe5c3153d9ae","before":"1fd4c890b02a2139f228922d264abc0ce0564854","commits":[{"sha":"96ec48afcde8b8689cbce09e6f8afe5c3153d9ae","author":{"email":"ea3cd978650417470535f3a4725b6b5042a6ab59@iernst.net","name":"Ryan Ernst"},"message":"Fix dynamic mapper when its parent already has an update\n\nThe change to move dynamic mapping handling to the end of document\nparsing has an edge case which can cause dynamic mappings to fail\ndocument parsing. If field a.b is added as an as part of the root update,\nfollowed by a.c.d, then we need to expand the mappers on the stack,\nsince a is hidden inside the root update which exists on the stack.\n\nThis change adds a test for this case, as well as tries to better\ndocument how the logic works for building up the stack before adding a\ndynamic mapper.","distinct":true,"url":"https://api.github.com/repos/rjernst/elasticsearch/commits/96ec48afcde8b8689cbce09e6f8afe5c3153d9ae"}]}