Along with user defined….
On March 15, 2018 at 22:40:33, Otto Fowler (ottobackwa...@gmail.com) wrote:
So looking at it, the standard way would be dynamic properties. Thank you
Andy.
On March 15, 2018 at 22:30:33, Otto Fowler (ottobackwa...@gmail.com) wrote:
I’m actually looking at doing a
So looking at it, the standard way would be dynamic properties. Thank you
Andy.
On March 15, 2018 at 22:30:33, Otto Fowler (ottobackwa...@gmail.com) wrote:
I’m actually looking at doing a web service processor , that would support
setting custom headers, and I want it to be “standard”.
I’ll
I’m actually looking at doing a web service processor , that would support
setting custom headers, and I want it to be “standard”.
I’ll look at the InvokeHTTP.
On March 15, 2018 at 15:57:33, Andy LoPresto (alopre...@apache.org) wrote:
Both of these are legacy processors introduced early on in
Hi Maribeth,
I am assuming you are building from the source tarball that was published
for 0.4.0. During the release process, we noticed some additional,
generated sources had made it into the tarball but did not want to waste
the time that already went into the release verification process.
Hi,
I was reminded that on the download page there is a comment
regarding the source release tarball:
"Note: If you experience any issues with building, please try
removing Scanner.cpp, Parser.hpp, Parser.cpp, *.hh from the
extensions/expression-language folder and rebuild"
This only
Hi,
What is your os? Did you use the cmake instructions or bootstrap?
On Mar 15, 2018 6:06 PM, "mjrudd...@gmail.com" wrote:
> I've been following the instructions for installing minifi, and everything
> worked up until i ran the 'make' command from the build folder.
I've been following the instructions for installing minifi, and everything
worked up until i ran the 'make' command from the build folder. Partway through
the make process, I get the following errors (see below). Has anyone seen this
before, and what can I do to fix it?
Thanks in advance for
I am not aware of ongoing efforts for this processor [1]. The release candidate
for 1.6.0 will be started early next week, so if you’re looking for it to make
that release, it might be a busy weekend.
[1] https://issues.apache.org/jira/browse/NIFI-2892
Hello all,
Is anyone actively working on a GetKinesis Processor? This is something that we
could really use, but do not want to duplicate effort.
If not, is there a timeline for this work and/or is there any chance of getting
this in the 1.6.0 release?
Thanks!
Adam Martini
Senior Dev, Nike
Both of these are legacy processors introduced early on in NiFi’s development
and intended for moving data between NiFi instances. I would recommend you use
InvokeHTTP, which is a more modern and full-featured processor and can perform
both GET and POST requests.
Andy LoPresto
Can someone explain or confirm why GetHTTP uses Dynamic Properties for
setting custom headers in http requests but PostHTTP uses a Property with a
Regex to pull flow file attributes?
Is it due to the forbidden input?
Thanks
ottO
11 matches
Mail list logo