Hi,
Based on your error message, the problem is most likely with your
truststore configuration. What did you configure for HTTPS in your
nifi.properties configuration file?
Pierre
Le 12 nov. 2017 19:38, "Nishant Gupta" a
écrit :
Hi Team,
I am trying to make site to site communication between
Hi Matt,
I'm using Jython in executescript because of my requirement.I cant switch to
groovy because I'm using packages supported by Python.Is there any way to
increase the speed of the executescript processor.Please help me with your
ideas.
Thanks,
Vyshali
--
Sent from: http://apache-nifi-dev
Hi Team,
I am trying to make site to site communication between 2 standalone nifi
instances.
I am getting below error
2017-11-12 23:44:41,304 WARN [Remote Process Group
b1265abf-015f-1000-632e-e7939fbad38f: https://X.X.X.X:9443/nifi Thread-1]
o.a.n.remote.StandardRemoteProcessGroup Unable to conn
I'll be sure to share my experiences as well. I found using Rancher
greatly aided in setting up a Kubernetes cluster on bare metal if that is
the route you are going.
On Sun, Nov 12, 2017, 12:27 john duggan wrote:
> +1.
>
> I haven't deployed NiFi into a Kubernetes cluster, but am planning some
+1.
I haven't deployed NiFi into a Kubernetes cluster, but am planning some
time over the next week to setup a POC (Proof of Concept) environment. I'm
certainly interested if anybody else already has experience in this area.
Hopefully, I can share my experience over the next week or two.
Regards
Hello,
If you are compiling MiNIFI C++ to run on another platform and/or cross
compiling for another platform please use the cmake portable flag.
This is traditionally done via cmake -DPORTABLE=ON ..
I will be submitting a PR to add this to our readme. I'll also be adding
this to our "Custo
I wanted to check with the group to see if anyone has deployed NiFi to a
Kubernetes cluster. If so, perhaps we could sync up on your lessons
learned. I am about to start looking at this myself. I am leaning towards
creating a NiFi Kubernetes Chart. Figured worth checking here first before
start
Hi Andy,
Sorry for the delayed response.
I like the idea of moving the capabilities out of core so that we can
decouple components for a variety of reasons that boil down to minimizing
work to break apart components in the future. I'm certainly not against
augmenting core to facilitate func