# Ingest node json to array

**URL:** <https://discuss.elastic.co/t/ingest-node-json-to-array/203434>\
**Category:** Вопросы на русском языке\
**Created:** [October 14, 2019, 10:57am UTC](https://discuss.elastic.co/t/ingest-node-json-to-array/203434 "2019-10-14T10:57:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lebedev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lebedev/32/53579_2.png) [@Lebedev](https://discuss.elastic.co/u/Lebedev)\
**Post date:** [October 14, 2019, 10:57am UTC](https://discuss.elastic.co/t/ingest-node-json-to-array/203434/1 "2019-10-14T10:57:41Z")

</div>

Коллеги, еще раз всем привет.  
Помогите решить проблему:

На входе поступают данные в большом количестве, следующего вида:

```auto
"_type": "_doc",
"_id": "yQ",
"_version": 1,
"_score": null,
"_source": {
"@timestamp": "2019-10-14T10:43:10.793Z",
"@version": "1",
"headers": {
"http_host": "elk_backend",
"request_path": "/",
"content_length": "90533",
"content_type": "application/json; charset=UTF-8",
"http_accept": null,
"accept_encoding": "gzip,deflate",
"http_version": "HTTP/1.1",
"request_method": "POST",
"http_user_agent": "Apache-HttpClient/4.5.8 (Java/1.8.0_121)"
},
"loggingMessages": [
{
"description": "Start",
"starttime": "2019",
"eventtype": "32",
"msgtype": "otb",
"mqmdmsgid": null,
"msgid": "6a1",
"messagestatusid": 0,
"reciever": "",
"mqmdcorrelid": null,
"procid": null,
"sender": "Test-1",
"exception": null
},
{
"description": "to",
"starttime": "2019",
"eventtype": "34",
"msgtype": "Rs",
"mqmdmsgid": "414",
"msgid": "219",
"messagestatusid": 0,
"reciever": "test2a",
"mqmdcorrelid": "000",
"procid": "ebb",
"sender": "Test2",
"exception": null
},

```

Как видно, поле loggingMessages имеет в своей структуре данные типа json, таких блоков json в поле loggingMessages достигает 100 возможно 300 блоков.

Когда не было высокой нагрузки эту задачу я решал через LS со следующим конфигом:

```auto
filter {
split {
field => "[loggingMessages]" }

```

Как только дали нагрузку со стороны источника данных, решено было перенести обработку на Iingest Node:

Со следующим конфигом:

```auto
{
"description" : "mq",
"processors" : [
{
"split": {
"field": "loggingMessages",
"separator": "\n"
}
}
]
}

```

В итоге получил следующую ошибку:

`[logstash.outputs.elasticsearch] retrying failed action with response code: 500 ({"type"=>"exception", "reason"=>"java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: field [loggingMessages] of type [java.util.ArrayList] cannot be cast to [java.lang.String]", "caused_by"=>{"type"=>"illegal_argument_exception", "reason"=>"java.lang.IllegalArgumentException: field [loggingMessages] of type [java.util.ArrayList] cannot be cast to [java.lang.String]", "caused_by"=>{"type"=>"illegal_argument_exception", "reason"=>"field [loggingMessages] of type [java.util.ArrayList] cannot be cast to [java.lang.String]"}}, "header"=>{"processor_type"=>"split"}})`

Подскажите, что делать? Для корректного разбора поля loggingMessages

---

<div class="post-metadata">

**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\
**Post date:** [October 14, 2019, 3:48pm UTC](https://discuss.elastic.co/t/ingest-node-json-to-array/203434/2 "2019-10-14T15:48:41Z")

</div>

Split в logstash-e разбивает одну запись на несколько, [split](https://www.elastic.co/guide/en/elasticsearch/reference/current/split-processor.html#split-processor) в узле ingest разбивает одну строку на несколько:

> Splits a field into an array using a separator character. Only works on string field

Эквивалентной функции в узле ingest, пока, к сожалению, нет.

---

<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:** [November 11, 2019, 3:48pm UTC](https://discuss.elastic.co/t/ingest-node-json-to-array/203434/3 "2019-11-11T15:48:42Z")

</div>

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