+1 (binding)
Ran through helper guide for validation.
Built on pop os and osx.
Ran a high throughout test flow, where I encountered no regressions across
several record oriented processors and non secure site to site.
Thanks,
Marc
On Tue, Jan 21, 2020, 4:43 PM Andrew Lim wrote:
> +1
+1 (non-binding)
-Ran full clean install on OS X (Catalina 10.15.2)
-Tested secure NiFi with secure NiFi Registry
-Ran basic flows successfully
-Reviewed core UI and documentation fixes/updates
In setting up my secure NiFi and secure NiFi registry, I used the NiFi TLS
Toolkit [1] to create my
+1 (binding)
Ran through release helper, tried various flows including some new
features (PutRecord, e.g.) PutRecord might not have made the
improvements list, changelog, release notes, etc. for 1.11 due to an
omission in Jira, but the Jira has since been corrected [1]
-Matt
[1]
+1
- Deploy on 3 node cluster in Azure
- Ran test data flow with high throughput
- Verified new changes in RC3
Looks good! Nice work everyone
On Tue, Jan 21, 2020 at 6:11 AM Arpad Boda wrote:
> +1
>
>- Verified signature, checksums.
>- Built properly.
>- Started NiFi, sent
Hi,
I am using NiFi invokeHttp processor to send the data to some other third
party server. The third party server is oauth2 protected, so I need to
login and get the JWT token after getting it, invoke http needs to add it
in header *'Authorization:"JWTtoken"'* before sending to third-party
The work for that would be part of NiFi so I don't think it is tied to
any specific registry release.
The REST APIs are already there in NiFi Registry, that is what the CLI
command for 'download-bundle' is calling.
On Tue, Jan 21, 2020 at 10:02 AM Mike Thomsen wrote:
>
> Is that slated for the
Dear Apache enthusiast,
(You’re receiving this message because you are subscribed to one or more
project mailing lists at the Apache Software Foundation.)
The call for presentations for ApacheCon North America 2020 is now open
at https://apachecon.com/acna2020/cfp
ApacheCon will be held at
Is that slated for the 1.0 release?
On Tue, Jan 21, 2020 at 9:33 AM Bryan Bende wrote:
> Hi Mike,
>
> There is no automatic retrieval from registry yet. Currently you would
> have to use CLI commands, or curl/scripts, to download the desired
> NARs from registry into the extensions folder on
Hello Team,
So far, it has been really nice experience with the advanced tool “Apache
NiFi”. We could progressed on a good amount on work. But now, it is time to
build some monitoring and alerting mechanism from the flow.
Could you please guide me on my question? I want to use the endpoints
Hi Mike,
There is no automatic retrieval from registry yet. Currently you would
have to use CLI commands, or curl/scripts, to download the desired
NARs from registry into the extensions folder on each node.
Thanks,
Bryan
On Tue, Jan 21, 2020 at 7:34 AM Mike Thomsen wrote:
>
> Bryan,
>
> I
+1
- Verified signature, checksums.
- Built properly.
- Started NiFi, sent flowfiles from MiNiFi, designed flow to handle
them.
Created https://issues.apache.org/jira/browse/NIFI-7049 in the meanwhile as:
- SFTP tests can fail on "clean" hosts
- The underlying behavior seems
> I cannot use a more recent version now due to the machine limitations
(Java version)
Can you share why you have that limitation?
On Tue, Jan 21, 2020 at 7:48 AM Fábio Coelho wrote:
> Hello,
>
>
>
> First of all thank you for the amazing framework.
>
>
>
> I’m building a prototype with NiFi
Hello,
First of all thank you for the amazing framework.
I'm building a prototype with NiFi 0.7.2, I cannot use a more recent version
now due to the machine limitations (Java version), and I'm trying to implement
a site-to-site (not secure) connection to send a flow file (from one NiFi
Bryan,
I tried this workflow:
1. Add NAR to extensions folder.
2. Add to canvas.
3. Stop NiFi and remove NAR and $NIFI/work to clear it out.
4. Restart NiFi
The NAR was not pulled from the v0.5 Registry I had running. Is that
expected behavior in 1.10 and 1.11?
Thanks,
Mike
On Mon, Oct 14,
14 matches
Mail list logo
