Torsten Bøgh Köster

Whoopsie, my bad, ran the `gradlew check` with `-Pvalidation.git.failOnModified=false`. Added license header in the last commit

I came across an edge case that I want to consider: In the distributed environment we should only ignore the `appends` section if we do not change the handler during...

Hey @epugh any chance to merge this? Or has anybody else directions for improvement?

Yes (I'm 95% sure): The macros don't get expanded on the shard. With the fix above the configuration is not picked up on the shard and the macros should stay...

I desperately needed the _s3_exporter_ for `arm64` architecture so I used your PR and forked the project to [observabilitystack/s3_exporter](https://github.com/observabilitystack/s3_exporter). `arm64` and `amd64` images are now published to [Docker Hub](https://hub.docker.com/r/observabilitystack/s3_exporter/tags) and...

It's not mandatory to use the `inMemory` implementation. In our cloud environment we build a new Zookeeper ensemble for every cluster. The Querqy rules are a part of the cluster's...

I know the consequences of using the `ClassicRewriteChainLoader`, that's what led to the PR in the first place. But by enforcing the usage of the in memory implementation you're actively...

 Let's build a bridge here to unstuck this issue. ### What are we doing? We're delivering readily packaged Solr-Docker containers containing all our tested Querqy rules. Clusters are initialized...

So? Any update on the bridge?

_@renekrie I urge you not to!_ Here's why: I see two use cases that actively use this feature for a good reason. I lay out both use cases below. I...