# Cannot remove field with ingest processor

**URL:** https://discuss.elastic.co/t/cannot-remove-field-with-ingest-processor/256828
**Category:** Elasticsearch
**Created:** [November 26, 2020, 10:58pm UTC](https://discuss.elastic.co/t/cannot-remove-field-with-ingest-processor/256828 "2020-11-26T22:58:00Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![egalpin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/egalpin/32/79772_2.png) [@egalpin](https://discuss.elastic.co/u/egalpin)
#### Post date: [November 27, 2020, 3:32am UTC](https://discuss.elastic.co/t/cannot-remove-field-with-ingest-processor/256828/2 "2020-11-27T03:32:27Z")

</div>

I believe this is happening because the notation used is interpreted as a JSON object path. For example, take a look at [flat\_settings](https://www.elastic.co/guide/en/elasticsearch/reference/current/common-options.html#_flat_settings).

I believe that the processor is expecting your document to look something like this:

```auto
{
      "_index": "original-index-2020.11",
      "_type": "_doc",
      "_id": "7K27Bas23a",
      "_version": 1,
      "_score": null,
      "_source": {
        "http”: {
            "request": {
                "auth": "-",
                "uri": "/xxxxx"
            }
        },
        "test": {
          "type": "SOFTWARE",
     
          "status": true
        },
...

```

Here’s a seemingly related forum post [How to handle dot in field names in ES 7.0](https://discuss.elastic.co/t/how-to-handle-dot-in-field-names-in-es-7-0/176511/8).

I think you may have to change the field names.

---

_[View the full topic](https://discuss.elastic.co/t/cannot-remove-field-with-ingest-processor/256828)._