# ELPASED Filter - Works differently 6.8.1 vs 7.1 - Possible Bug?

**URL:** <https://discuss.elastic.co/t/elpased-filter-works-differently-6-8-1-vs-7-1-possible-bug/187400>\
**Category:** Logstash\
**Created:** [June 25, 2019, 5:42pm UTC](https://discuss.elastic.co/t/elpased-filter-works-differently-6-8-1-vs-7-1-possible-bug/187400 "2019-06-25T17:42:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [June 26, 2019, 3:38pm UTC](https://discuss.elastic.co/t/elpased-filter-works-differently-6-8-1-vs-7-1-possible-bug/187400/2 "2019-06-26T15:38:48Z")

</div>

In V7, where the java execution engine became the default, logstash does not preserve the order of lines in the file, even with '--pipeline.workers 1'. Thus the end is processed before the begin, so you get a "elapsed\_end\_without\_start" tag.

For now you could set 'pipeline.java\_execution: false' in logstash.yml, but I do not expect elastic to maintain two engines, eventually java will be the only option.

---

_[View the full topic](https://discuss.elastic.co/t/elpased-filter-works-differently-6-8-1-vs-7-1-possible-bug/187400)._