Hello Anthony, Sorry for the late reply. First thanks a lot for your contributions to JMeter eco-system and for this particular initiative. I think your plugin is a great addition to JMeter. ElasticSearch is a standard today and having a plugin for it is great.
But I am wondering if we need this in the core as it means for the team: - More code to maintain - More dependencies on potentially future incompatible licenses (Redis story without any value judgment on that) Looking at the code of PR, I see there is maybe some room for increasing test coverage. What makes you contribute the plugin today to the core as it can stay as a 3rd party plugin as it lives today for example ? @ Team, what's your thoughts on this ? Thanks Regards On Mon, Sep 14, 2020 at 10:01 PM Anthony Gauthier < [email protected]> wrote: > Hi everyone, > > I'm the author of the ElasticSearch Backend Listener plugin for JMeter. > After 3 years of developing and maintaining the plugin, I figured it was > way overdue to incorporate it in the main JMeter codebase. I've already > created a PR on GitHub; here's the link to it: > > https://github.com/apache/jmeter/pull/615 > > If any of you have any questions or comments I'd appreciate it a lot, > either through emails or via the PR itself. > Thanks, > > *Anthony Gauthier* > https://www.github.com/delirius325 > https://www.linkedin.com/in/anthonygau > -- Cordialement. Philippe Mouawad.
