# Logstash pipeline systax errors after 7.6.0

**URL:** https://discuss.elastic.co/t/logstash-pipeline-systax-errors-after-7-6-0/220903
**Category:** Logstash
**Created:** [February 25, 2020, 6:02pm UTC](https://discuss.elastic.co/t/logstash-pipeline-systax-errors-after-7-6-0/220903 "2020-02-25T18:02:17Z")
**Posts on this page:** 1
**Showing post:** 12

<div class="post-metadata">

### Author: ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)
#### Post date: [February 26, 2020, 7:24pm UTC](https://discuss.elastic.co/t/logstash-pipeline-systax-errors-after-7-6-0/220903/12 "2020-02-26T19:24:23Z")

</div>

In 7.6.0, changes were introduced to add source-file metadata to nodes ([elastic/logstash#11456](https://github.com/elastic/logstash/pull/11456)), which was intended to provide greater visibility when debugging pipelines that were composed of many source files. An untended consequence of this is that by parsing the files individually instead of pre-concatenating them, we no longer could parse configurations whose individual files weren't syntactically complete ([elastic/logstash#11598](https://github.com/elastic/logstash/issues/11598)). Work is ongoing to find a solution that gets us this source-file metadata in a manner that restores in-the-wild composition styles.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-pipeline-systax-errors-after-7-6-0/220903)._