nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Witt <>
Subject Re: NIFI-4198 - *ElasticsearchHttp processors do not expose Proxy settings
Date Sat, 12 Aug 2017 19:24:37 GMT

Very cool that you are planning to jump in on this.  Your approach
sounds like a good start.  As far as system testing you're hitting on
one of the more challenging parts of the equation here.  Your unit
tests of course won't integrate with a real ES instance but manual
testing can be done against a system as you mention.  I think a lot of
folks use things like Docker to do such testing or sometimes these
systems offer quick start configurations.  You could put a squid proxy
instance/container in front as well.  Perhaps this one can help


On Sat, Aug 12, 2017 at 11:49 AM, Arun Manivannan <> wrote:
> Hi,
> Very Good morning.
> I would like to make an attempt at resolving NIFI-4198
> <>.  Looking at the code, I
> would think by introducing the proxy url and authentication properties and
> delegating them to the OkHttpClient would be a good way to do it.
> The question I have is beside the test cases, I would like to test it
> against an actual elastic server to be absolutely sure of the fix.  What's
> the easiest/good way to run an elastic instance behind a proxy and test the
> modified component?
> Thanks in advance.
> Cheers,
> Arun

View raw message