# Elasticsearch: JSON processor issue in Elastic V7.8.1

**URL:** <https://discuss.elastic.co/t/elasticsearch-json-processor-issue-in-elastic-v7-8-1/247360>\
**Category:** Elasticsearch\
**Created:** [September 3, 2020, 9:57am UTC](https://discuss.elastic.co/t/elasticsearch-json-processor-issue-in-elastic-v7-8-1/247360 "2020-09-03T09:57:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hung\_M\_Le](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hung_m_le/32/54995_2.png) [@Hung\_M\_Le](https://discuss.elastic.co/u/Hung_M_Le)\
**Post date:** [September 3, 2020, 9:57am UTC](https://discuss.elastic.co/t/elasticsearch-json-processor-issue-in-elastic-v7-8-1/247360/1 "2020-09-03T09:57:49Z")

</div>

Hi

I have followed the example outlined inside the document about the JSON processor:

[https://www.elastic.co/guide/en/elasticsearch/reference/6.8/json-processor.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/json-processor.html)

Here is the code:

```
{
  "json" : {
    "field" : "status_report",
    "target_field" : "status_report_json",
    "ignore_failure" : true
  }
}

```

Questions:

1. I noticed in the TABLE view, the JSON processor does not decode the JSON if there is a list of complex structure. In the example below, there are 2 fields that was not decoded: a) coordinates, b) area\_details. I would like to find out if this is a known limitation or there is something that can be done to fully decode these fields?

2. I also noticed that in the JSON view, the JSON string has been decoded correctly. This is different from the TABLE view, where I noticed some failure (Please refer to the picture that I capture and uploaded here)

3. Is the above target\_field ("status\_report\_json") will be created by the JSON processor without being predefined. Is it expected? I try to define this field inside the fields.yml, but this change does not work - Java execption error!

Here is the JSON structure:

"status\_report": "{"summary":{"status":"SUCCESS","last\_checked\_time":1599035573,"total\_size":128914936},"area\_detail":{"area\_type":"HOME\_AREA","area\_geometry":{"type":"BBOX","coordinates":[{"lat":32.507170148650867,"lon":-97.11751645451773},{"lat":33.04615931912257,"lon":-97.11751645451773},{"lat":33.04615931912257,"lon":-96.4764624273182},{"lat":32.507170148650867,"lon":-96.4764624273182}]},"layer\_details":[{"layer":"JUNCTION\_VIEW","state":"COMPLETED","status":"SUCCESS","size":11495984,"created\_time":1599035342,"updated\_time":1599035557},{"layer":"LANDMARK","state":"COMPLETED","status":"SUCCESS","size":6574073,"created\_time":1599035342,"updated\_time":1599035573},{"layer":"STREET","state":"COMPLETED","status":"SUCCESS","size":14518781,"created\_time":1599035342,"updated\_time":1599035345},{"layer":"MAP","state":"COMPLETED","status":"SUCCESS","size":84938399,"created\_time":1599035342,"updated\_time":1599035436},{"layer":"POI","state":"COMPLETED","status":"SUCCESS","size":11359236,"created\_time":1599035342,"upd

 ![Screen Shot 2020-09-03 at 1.50.30 AM](https://us1.discourse-cdn.com/elastic/original/3X/4/c/4cc1091d9957eb5f228c0bbe70d4a3fb712b4736.png) ated\_time":1599035347},{"layer":"ADMIN","state":"COMPLETED","status":"SUCCESS","size":28463,"created\_time":1599035342,"updated\_time":1599035348},{"layer":"KNOWLEDGE","state":"COMPLETED","status":"NO\_UPDATE","size":0,"created\_time":1599035342,"updated\_time":1599035342}]}}",

---

<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:** [October 1, 2020, 9:57am UTC](https://discuss.elastic.co/t/elasticsearch-json-processor-issue-in-elastic-v7-8-1/247360/2 "2020-10-01T09:57:53Z")

</div>

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