# Elasticsearch mapping \_parsing\_exception **URL:** \ **Category:** Elasticsearch\ **Created:** [August 23, 2019, 4:08pm UTC](https://discuss.elastic.co/t/elasticsearch-mapping-parsing-exception/196561 "2019-08-23T16:08:49Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Vishnu\_Singhal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishnu_singhal/32/52488_2.png) [@Vishnu\_Singhal](https://discuss.elastic.co/u/Vishnu_Singhal)\ **Post date:** [August 23, 2019, 4:08pm UTC](https://discuss.elastic.co/t/elasticsearch-mapping-parsing-exception/196561/1 "2019-08-23T16:08:50Z")
Hi, I'm using ELasticsearch as docker . I havent created mapping indexes there . I'm getting following exception org.apache.spark.SparkException: Job aborted due to stage failure: Task 43 in stage 516846.0 failed 4 times, most recent failure: Lost task 43.3 in stage 516846.0 (TID 5945113, 10.244.18.196, executor 4): org.apache.spark.util.TaskCompletionListenerException: Could not write all entries for bulk operation [1/2]. Error sample (first [5] error messages): org.elasticsearch.hadoop.rest.EsHadoopRemoteException: mapper\_parsing\_exception: failed to parse;org.elasticsearch.hadoop.rest.EsHadoopRemoteException: illegal\_argument\_exception: object field starting or ending with a [.] makes object resolution ambiguous: [../../../../../../../../../../../../../../../etc/passwd] {"index":{"\_id":"435154|3189f8ce-fad5-44c6-ad7c-ec6c66679aa3|WEB|/apply/application"}} {"service\_id":"3189f8ce-fad5-44c6-ad7c-ec6c66679aa3","src\_group":"WEB","src\_id":"/apply/application","txn\_count":6,"destination\_map":{"/var/log":1,"cp /etc/passwd /tmp/":1,"[http://localhost:8281/http/get":2,"../../../../../../../../../../../../../../../etc/passwd":1,"](http://localhost:8281/http/get%22:2,%22../../../../../../../../../../../../../../../etc/passwd%22:1,%22)\\&xxe;":1},"ss\_map":{"SSRF":2,"DIRECTORY":1,"READFILE":2,"COMMAND":1},"app\_id":"d2f5d24d-89fc-49b9-8237-83e844a147fe","interval":18131,"interval\_type":"DAILY","doc\_id":"435154|3189f8ce-fad5-44c6-ad7c-ec6c66679aa3|WEB|/apply/application","hour\_interval":0} What could be best solution? ---
**Author:** ![Vishnu\_Singhal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishnu_singhal/32/52488_2.png) [@Vishnu\_Singhal](https://discuss.elastic.co/u/Vishnu_Singhal)\ **Post date:** [August 26, 2019, 4:28am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-parsing-exception/196561/2 "2019-08-26T04:28:03Z")
Can anyone check on this ? Elasticsearch version is 7.3.1 ---
**Author:** ![Hamilton74](https://avatars.discourse-cdn.com/v4/letter/h/e68b1a/32.png) [@Hamilton74](https://discuss.elastic.co/u/Hamilton74)\ **Post date:** [August 26, 2019, 4:36am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-parsing-exception/196561/3 "2019-08-26T04:36:18Z")
I checked but it is giving some unexpected errors[.](https://www.mywegmansconnect.us/) ---
**Author:** ![Vishnu\_Singhal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishnu_singhal/32/52488_2.png) [@Vishnu\_Singhal](https://discuss.elastic.co/u/Vishnu_Singhal)\ **Post date:** [August 26, 2019, 4:37am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-parsing-exception/196561/4 "2019-08-26T04:37:11Z")
because of the dot in the field name. Is there a way by some POST/PUT call to allow dot in the mappings ? ---
**Author:** ![wangqinghuan](https://avatars.discourse-cdn.com/v4/letter/w/d26b3c/32.png) [@wangqinghuan](https://discuss.elastic.co/u/wangqinghuan)\ **Post date:** [August 26, 2019, 4:40am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-parsing-exception/196561/5 "2019-08-26T04:40:26Z")
Why don't you rename the name of dot-prefix field ? ---
**Author:** ![Vishnu\_Singhal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishnu_singhal/32/52488_2.png) [@Vishnu\_Singhal](https://discuss.elastic.co/u/Vishnu_Singhal)\ **Post date:** [August 26, 2019, 4:42am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-parsing-exception/196561/6 "2019-08-26T04:42:38Z")
i can do that. But looking for the property to disable the check . I found replace\_dots\_in\_field\_names/allow\_dots\_in\_name which is default set to false. How can i update this for a given index without restarting elasticsearch ? ---
**Author:** ![wangqinghuan](https://avatars.discourse-cdn.com/v4/letter/w/d26b3c/32.png) [@wangqinghuan](https://discuss.elastic.co/u/wangqinghuan)\ **Post date:** [August 26, 2019, 4:55am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-parsing-exception/196561/7 "2019-08-26T04:55:10Z")
From v 5.0, the dots are pemitted in each filed and each step in path represents a object. [https://www.elastic.co/guide/en/elasticsearch/reference/2.4/dots-in-names.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/dots-in-names.html) And your problem is field starting with a dot, which makes a object resolution ambiguous.I recommend you rename field. ---
**Author:** ![Vishnu\_Singhal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishnu_singhal/32/52488_2.png) [@Vishnu\_Singhal](https://discuss.elastic.co/u/Vishnu_Singhal)\ **Post date:** [August 26, 2019, 5:20am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-parsing-exception/196561/8 "2019-08-26T05:20:06Z")
Do we have an API to disable index on a field in index? ---
**Author:** ![wangqinghuan](https://avatars.discourse-cdn.com/v4/letter/w/d26b3c/32.png) [@wangqinghuan](https://discuss.elastic.co/u/wangqinghuan)\ **Post date:** [August 26, 2019, 5:25am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-parsing-exception/196561/9 "2019-08-26T05:25:36Z")
The "index" option for a field determine whether a field can be searchable(indexed). [https://www.elastic.co/guide/en/elasticsearch/reference/7.3/mapping-index.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.3/mapping-index.html) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 23, 2019, 5:35am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-parsing-exception/196561/10 "2019-09-23T05:35:49Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.