Hi Bas,
Sorry for the late reply.
Thanks for the clarification, I over simplified the flow. As you
experienced, NiFi back pressure is handled per relationship and as
long as a relationship has room to receive new flow files, source
processor is scheduled to run.
I don't think there's an
Hi
I am developing custom processor with hive database connection pooling
service. Added necessary dependency in pom file and added necessary folders
in custom processor folder. I have created class file and able to generate
nar file. Placed nar file in lib directory and restarted nifi server.
I have been running a standalone instance of Nifi and am preparing a move
into a cluster configuration. One aspect I am curious about is how
ControlRate is going to operate with n nodes. I am using control rate to
satisfy rate-limit requirements for external services.
My flow looks something
Thanks Matt
On Wed, Feb 8, 2017 at 3:22 PM, Matt Burgess wrote:
> Mohammed,
>
> HandleHttpRequest [1] allows you to specify the listening port as well
> as Allowed Paths. Using the hostname/IP of the NiFi instance, along
> with the Listening Port and Allowed Paths, creates
Mohammed,
HandleHttpRequest [1] allows you to specify the listening port as well
as Allowed Paths. Using the hostname/IP of the NiFi instance, along
with the Listening Port and Allowed Paths, creates an endpoint to
which you can issue HTTP commands (GET, PUT, POST -- all can be
allowed or denied
Hi
I'm sorry if the question is silly, but it is giving me a hard time. We
have a web page that contain some inputs (e.g., userid and other
parameters) and I want to sent these parameters to a remote nifi-instance.
I think I should use "handlHTTPRequst" processor at the remote instance,
but I'm
Hi Aldrin,
This was with the original package. Also, I’ve attached the verbose output.
Thanks,
Dan
From: Aldrin Piri [mailto:aldrinp...@gmail.com]
Sent: Tuesday, February 07, 2017 5:18 PM
To: users@nifi.apache.org
Subject: Re: GetTwitter - Security/Certificate Issue
Hi Dan,
Was this with an
Prabhu,
There are a couple of ways I can think of for NiFi to be able to
communicate with an external application:
1) The InvokeHttp processor [1] can send the flow file content as the
payload and any number of flow file attributes as HTTP headers (you
can specify a regular expression for which