# Problem with parsing fields starts or ends with dot(.)

**URL:** <https://discuss.elastic.co/t/problem-with-parsing-fields-starts-or-ends-with-dot/211978>\
**Category:** Logstash\
**Created:** [December 16, 2019, 10:29am UTC](https://discuss.elastic.co/t/problem-with-parsing-fields-starts-or-ends-with-dot/211978 "2019-12-16T10:29:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![atahanceylan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atahanceylan/32/58691_2.png) [@atahanceylan](https://discuss.elastic.co/u/atahanceylan)\
**Post date:** [December 16, 2019, 10:29am UTC](https://discuss.elastic.co/t/problem-with-parsing-fields-starts-or-ends-with-dot/211978/1 "2019-12-16T10:29:31Z")

</div>

Hi,

From nested json fields some fields starts with dot or ends with dot this causing problem on Elasticsearch "Object field starting or ending with a [.] makes object resolution ambiguous: ]"

What is the best optimal solution for this issue?

---

<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:** [January 13, 2020, 10:29am UTC](https://discuss.elastic.co/t/problem-with-parsing-fields-starts-or-ends-with-dot/211978/2 "2020-01-13T10:29:32Z")

</div>

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