# Multiline codec discrepancies between file and stdin inputs

**URL:** <https://discuss.elastic.co/t/multiline-codec-discrepancies-between-file-and-stdin-inputs/47686>\
**Category:** Logstash\
**Created:** [April 18, 2016, 5:09pm UTC](https://discuss.elastic.co/t/multiline-codec-discrepancies-between-file-and-stdin-inputs/47686 "2016-04-18T17:09:50Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![guyboertje](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guyboertje/32/31592_2.png) [@guyboertje](https://discuss.elastic.co/u/guyboertje)\
**Post date:** [April 25, 2016, 9:10am UTC](https://discuss.elastic.co/t/multiline-codec-discrepancies-between-file-and-stdin-inputs/47686/7 "2016-04-25T09:10:47Z")

</div>

The multiline codec ignoring blank lines side-effect was introduced in 0.1.4 on January 27 2015, to cope with inputs that supplied text with embedded newline characters - the upside, the text was split on newlines and the resulting array of lines was fed to multiline - the downside, text containing only one newline, when split gives an empty array, effectively ignoring the empty line.

It is a bit harder to say exactly which version of Logstash has this codec version.

I think it is reasonable to expect behavioural changes when making such a big step (from 1.5.X to 2.2.X)

---

_[View the full topic](https://discuss.elastic.co/t/multiline-codec-discrepancies-between-file-and-stdin-inputs/47686)._