Re: 1.11.3 trust store error

https://protonmail.com) Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐ > On Tuesday, March 3, 2020 12:40 PM, Ryan Ward > wrote: > > > Hi Joe - Did you resolve your issue? If so I am wondering what the fix > was as I'm seeing the same error on my cluster. > > > > On Thu,

Re: 1.11.3 trust store error

Hi Joe - Did you resolve your issue? If so I am wondering what the fix was as I'm seeing the same error on my cluster. On Thu, Feb 27, 2020 at 3:13 AM Endre Kovacs wrote: > Hi Joe, > > 1. Have you tried connecting/debugging with openssl? From one pod to the > other: > (openssl s_client

Re: NIFI-6150

Our content repo (7 tb) will fill up if not restarted ever few hours, we had to fall back to 1.8. On Wed, Mar 27, 2019 at 10:50 AM BINLEI XUE wrote: > Me too > > On Wed, Mar 27, 2019 at 10:47 PM Ryan Ward wrote: > > > I just came across NIFI-6150 and was wondering

NIFI-6150

I just came across NIFI-6150 and was wondering if there are plans to release 1.9.2?

Re: putTCP odd behavior with EL

ate against flows when "Connection Per Flow > File" is true b/c then we can create a new one every time, but when it > is false it means you would have to potentially keep open many > connections. > > It also may be confusing though to have differing evaluation based on &

Re: putTCP odd behavior with EL

t;marcogaid...@gmail.com> > > wrote: > > > Hi Ryan, > > > > > > probably the reason of the behavior is that EL on PutTCP is enabled but > > it > > > is not run on the incoming flowfile. So it doesn't care the attributes > of > > &

putTCP odd behavior with EL

I'm seeing odd behavior trying to use attributes for the hostname and port fields. using ${endpoint_port} (9003) + hardcoded IP results in flowfile yielding failed to process session due to java.lang.NumberFormatException: For input string: "": {} java.lang.NumberFormatException: For input

Re: FetchSFTP vs GetSFTP

esting experiment. It makes the > code more challenging to write though, not that that's a reason not to > do it. > > If you have a 5 node cluster, you are doing List on primary node and > then redistributing the results to all the nodes via an RPG so all > nodes can fetch? > &g

Re: FetchSFTP vs GetSFTP

Witt <joe.w...@gmail.com> wrote: > > Ryan - dont know the code specifics behind FetchSFTP off-hand but i > > can confirm there are users at that range for it. > > > > Thanks > > > > On Tue, Oct 31, 2017 at 11:38 AM, Ryan Ward <ryan.wa...@gmail.com>

FetchSFTP vs GetSFTP

I've found that on a single node getSFTP is able to pull more files off a remote server than Fetch in a cluster. I noticed Fetch doesn't have a max selects so it is requiring way more connections (one per file?) and concurrent threads to keep up. Was wondering if anyone is using List/Fetch at

Re: Binary Data over the PutTCP processor

Bryan - I started to evaluate putTCP and agree Outgoing Message Delimiter should be optional. I'm currently having to splitText to 1 in order to use putTCP which doesn't seem like the most efficient approach. Was a JIRA ever created for this capability? On Wed, Sep 14, 2016 at 4:41 PM, Bryan

Re: [DISCUSS] NiFi 1.1.0 release

Joe - Is there a target date for 1.1? On Thu, Oct 27, 2016 at 10:50 AM, Joe Witt wrote: > Team, > > Just an update on things with working toward an Apache NiFi 1.1.0 > release. There are still about 33 JIRAs there now and some are > awaiting review and are some are under

Re: putTCP nifi 0.7?

lable" tickets to see which of them can > be finished off for 0.7.0 and ping the appropriate committers to help out. > > Joe > - - - - - - Joseph Percivall > linkedin.com/in/Percivall > e: joeperciv...@yahoo.com > > > > > > On Thursday, June 16, 2016 2:00 PM, Ryan Ward <ryan.wa...@gmail.com> > wrote: > Will this one make 0.7? > > https://issues.apache.org/jira/browse/NIFI-1834 >

putTCP nifi 0.7?

Will this one make 0.7? https://issues.apache.org/jira/browse/NIFI-1834

Re: [ANNOUNCE] New Apache NiFi Committer Michael Moser

Congrats Moser! On Oct 18, 2015 4:29 PM, "Joey Echeverria" wrote: > Congratulations Michael! > > > On Oct 18, 2015, at 12:26, Joe Witt wrote: > > > > NiFi Community, > > > > On behalf of the Apache NiFI PMC, I am very pleased to announce that > > Michael