I want to make remote service invokation in nifi and i want to make one
flowfile for each startDate reponse here is my ecexutescript code for it,
but i want to konw how can i prevent service invokation as soon as i receve
bad request for example if service doesn't have data for
startDate=2017-07-07
MiNiFi cpp devs,
Very recently I started getting this unexpected compilation error in the ‘make
docker’ target. I double-checked the packages we are installing in the
Dockerfile, and it does include curl-dev, so I’m confused why we’d be seeing
this. Is it perhaps a curl version issue?
[ 3%] P
Looking through some alpine package contents here:
https://pkgs.alpinelinux.org/contents?file=&path=&name=curl-dev&branch=v3.6&repo=main&arch=x86_64
I see that curlbuild.h has not been part of that package. Is this something new
we added?
When I search specifically for curlbuild.h, I see a coup
Andy,
In a branch I've been working on, I happened upon those ( curlbuild.h
and easy.h which I believe are unnecessary ) , which were removed elsewhere
but apparently I didn't see them here due to copy/paste of some code and
removed them without issue.
On Wed, Aug 16, 2017 at 10:30 AM, Andy Chr
OK. I created MINIFI-376 [1] to track the issue. I take it the fix is to remove
the references? Do you recommend for this to be done in a bug fix branch, or
will it be taken care of in one of your upcoming merges?
[1] https://issues.apache.org/jira/browse/MINIFI-376
Regards,
Andy I.C.
On 8/16
Andy,
I believe the correct course of action is to resolve the code so that we
don't have duplicate code. This was found quite some time ago in the
original code that was copied, but unfortunately I wasn't aware the error
was propagated. I've resolved the duplicate code, and hence the error in a
Submitted PR 128 [1] which resolves the build issue by removing references to
curlbuild.h.
[1] https://github.com/apache/nifi-minifi-cpp/pull/128
Regards,
Andy I.C.
On 8/16/17, 11:13 AM, "Marc" wrote:
Andy,
I believe the correct course of action is to resolve the code so that we
Andy,
Thank you for your reply. I have come up with a scheme which should meet our
needs. It involves using a key/value approach similar to the idea behind the
Variable Registry but is file based. Key/value pairs are stored in JSON files
for each template and I have a Python program whic
