# Adding field creates an array not a static string

**URL:** <https://discuss.elastic.co/t/adding-field-creates-an-array-not-a-static-string/258149>\
**Category:** Logstash\
**Created:** [December 9, 2020, 3:27pm UTC](https://discuss.elastic.co/t/adding-field-creates-an-array-not-a-static-string/258149 "2020-12-09T15:27:08Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [December 9, 2020, 5:15pm UTC](https://discuss.elastic.co/t/adding-field-creates-an-array-not-a-static-string/258149/5 "2020-12-09T17:15:59Z")

</div>

Are you expecting that each configuration file will automatically get run in a separate pipeline? That does not happen unless you configure it that way using pipelines.yml. If you point path.config (or -f) at a directory that contains more than one configuration file then they are combined. So if you have two files

```
input { http { ... } }
filter { mutate { ... } }
output { stdout {... } }

```

and

```
input { file { ... } }
filter { csv { ... } }
output { elasticsearch {... } }

```

that is equivalent to

```
input {
    http { ... }
    file { ... }
}
filter {
    mutate { ... }
    csv { ... }
}
output {
    stdout {... }
    elasticsearch {... }
}
```

---

_[View the full topic](https://discuss.elastic.co/t/adding-field-creates-an-array-not-a-static-string/258149)._