# Error: Object field starting or ending with \[.\]

**URL:** <https://discuss.elastic.co/t/error-object-field-starting-or-ending-with/108994>\
**Category:** Elasticsearch\
**Created:** [November 24, 2017, 9:13am UTC](https://discuss.elastic.co/t/error-object-field-starting-or-ending-with/108994 "2017-11-24T09:13:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dC7](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dC7](https://discuss.elastic.co/u/dC7)\
**Post date:** [November 24, 2017, 9:13am UTC](https://discuss.elastic.co/t/error-object-field-starting-or-ending-with/108994/1 "2017-11-24T09:13:17Z")

</div>

Our service is logging via fluentd to elasticsearch and I've been starting recently to fix all errors seen in the Fluentd-Logs (so I'm not quite sure if I should ask here or the fluentd-team).

I'm nearly done, but I have no idea how to find and fix this one or what it acutally means:

```
"error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse", "caused_by"=>{"type"=>"illegal_argument_exception", "reason"=>"object field starting or ending with a [.] makes object resolution ambiguous: [\v]"}}

```

I've looked through all used object fields but no one is having a "." in it.

It would be great if someone would know how to tackle this error

---

<div class="post-metadata">

**Author:** ![rjernst](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rjernst/32/6363_2.png) [@rjernst](https://discuss.elastic.co/u/rjernst)\
**Post date:** [November 27, 2017, 4:56pm UTC](https://discuss.elastic.co/t/error-object-field-starting-or-ending-with/108994/2 "2017-11-27T16:56:30Z")

</div>

Can you look at your elasticsearch log files to see the full stack trace? You should see another exception which contains the name of the field being parsed.

---

<div class="post-metadata">

**Author:** ![dC7](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dC7](https://discuss.elastic.co/u/dC7)\
**Post date:** [December 5, 2017, 4:01pm UTC](https://discuss.elastic.co/t/error-object-field-starting-or-ending-with/108994/3 "2017-12-05T16:01:40Z")

</div>

I looked at the log files and the entries just look like the following (shortened) one

```
Could not push log to Elasticsearch: 
{"took"=>182, "errors"=>true, "items"=>[
<a lot of working ones>,
{"index"=>
 {"_index"=>"some-service-log-2017.12.05", "_type"=>"some-service", "_id"=>"AWAmgPHDW8acwW_CgGC0", "status"=>400, "error"=>
  { "type"=>"mapper_parsing_exception", "reason"=>"failed to parse", "caused_by"=>
   {"type"=>"illegal_argument_exception", "reason"=>"object field starting or ending with a [.] makes object resolution ambiguous: [\v]"}
  }
 }
}
, <some more entries>
]}

```

I couldn't find any other exceptions (for this index) in there.

But after looking at the Index Patterns (in Kibana) again, I was able to find a strange looking field (mapped as object) ending with ".[a few spaces]"

I remapped the field to text and found out that this was the problem.

Thanks for your help.

---

<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 2, 2018, 4:01pm UTC](https://discuss.elastic.co/t/error-object-field-starting-or-ending-with/108994/4 "2018-01-02T16:01:48Z")

</div>

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