Lucas Bremgartner

@jgough I will have a look at this. It looks like it is resolvable, because passing `@metadata` works for me in the `fields` in `testcases` (nested instead of Logstash syntax)...

I looked into this a little bit more and it looks like we have two issues: 1. addressing `@metadata` fields with Logstash config syntax (`[@metadata][field]`) does not work. 2. Nested...

OK, if I got this right, the proposal from @jgough is exactly what @magnusbaeck has sumarized in > The `[field][subfield]` syntax could result in deep merging while specifying a full...

I think the generalized algorithm for this would go like this: 1. start with an empty target object 2. for all "non Logstash syntax" keys in the global fields object,...

I did a first iteration to implement the above specification, but it is not as straight forward as I initially though. There are a lot of edge cases which we...

@magnusbaeck I went through all the version 2.0 related issues and tried to compile a TODO list for the remaining work. This is what I have found so far (this...

I added a helper command to LFV to download and install Logstash. This allowed me to easily test the current state with different versions of Logstash. So far, the current...

As found out already earlier, the event ordering in the pipeline has been reintroduced in Logstash 7.7.0 (see https://www.elastic.co/guide/en/logstash/current/logstash-7-7-0.html#_improving_the_java_pipeline_execution_engine). According to the change log entry, the event ordering has been...

@matejzero Thanks for the hint. I added the mentioned workaround and I successfully executed the integration tests of the current state with some more versions of Logstash: * 7.0.0 *...

I made some more progress on the Logstash daemon mode compatibility front. After some tweaking (https://github.com/breml/logstash-filter-verifier/commit/c21939c9ab3da421ad67a4e5254344bbbebd6444), I successfully executed the integration tests with the following Logstash releases: * 6.8.15 *...