This is very helpful. Thank you very much Pierre. -Jim
On Wed, Feb 8, 2017 at 2:44 AM, Pierre Villard
wrote:
> James,
>
> If you always want to return 200 as HTTP response whatever the request is,
> then you could have:
> HandleHttpRequest directly linked to HandleHttpResponse with property
> st
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 a
Dear Apache Enthusiast,
This is your FINAL reminder that the Call for Papers (CFP) for ApacheCon
Miami is closing this weekend - February 11th. This is your final
opportunity to submit a talk for consideration at this event.
This year, we are running several mini conferences in conjunction with
t
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 u
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 n
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 v
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 an endpoint to
> which
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 like:
Hey team, I have a ConsumeKafka_0_10 running which normally operates
without problems. I had a queue back up due to a downstream processor and I
started getting these bulletins.
01:16:01 UTC WARNING a46d13dd-3231-1bff-1a99-1eaf5f37e1d2
ConsumeKafka_0_10[id=a46d13dd-3231-1bff-1a99-1eaf5f37e1d2] Dup
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. Its
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 existing
11 matches
Mail list logo