# Space in Key Value Pipeline

**URL:** https://discuss.elastic.co/t/space-in-key-value-pipeline/371018
**Category:** Elasticsearch
**Tags:** ingest-pipeline
**Created:** [November 25, 2024, 11:30am UTC](https://discuss.elastic.co/t/space-in-key-value-pipeline/371018 "2024-11-25T11:30:31Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Patryk\_Ostrowski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patryk_ostrowski/32/111965_2.png) [@Patryk\_Ostrowski](https://discuss.elastic.co/u/Patryk_Ostrowski)
#### Post date: [November 25, 2024, 11:30am UTC](https://discuss.elastic.co/t/space-in-key-value-pipeline/371018/1 "2024-11-25T11:30:31Z")

</div>

Hello,  
I need to use the Key-Value processor to extract fields using Ingest Pipeline. Unfortunately, there are spaces in the field value. How do they have such a log extract the fields.

```auto
field=1 field2=2 field3=Nov 25 2024, 09:00:19 UTC field4=5

```

I can't use dissect because the logs have different structure. My idea is to use gsub. In the case of logstash I found such a hint. mutate { gsub =\> `[“message”, “(\S+=)”, “, \1”] }` however \1 in ingest pipline gives 1.
