RE: [EXT] Re: Direct access to FlowFile Content Repository Path?

2019-03-04 Thread Peter Wicks (pwicks)
Thanks Joe. The data sources out of a database (ExecuteSQL). Content Repository is not an area where I'm very knowledgeable on the internals. Thanks again. -Original Message- From: Joe Witt Sent: Monday, March 4, 2019 10:05 PM To: dev@nifi.apache.org Subject: [EXT] Re: Direct access

Re: Direct access to FlowFile Content Repository Path?

2019-03-04 Thread Joe Witt
Peter It is not possible and if it were it would only be available for repo implementations that use files and further would need to be limited to cases where the content on disk was in a file by itself (unlikely) or for processes that would honor the offsets and length, would be read only, etc..

Re: Not able to connect through site-to-site remote professor group to the last nifi in a nifi chaining

2019-03-04 Thread Puspak
Thank a lot Koji for the response . The issue was because of the trailing white space as you have mentioned . Regards -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Direct access to FlowFile Content Repository Path?

2019-03-04 Thread Peter Wicks (pwicks)
I'm working on a custom processor. The processor calls a 3rd party library that needs the path to my FlowFile content (no streams/arrays, just file names). I could write the content out to a temp file, but the content is already right there in the content repository... and many of the files are

Re: SSLHandshake Exception from Site-to-Site

2019-03-04 Thread Koji Kawamura
Hi Nadeem, How many S2S clients are connecting to your NiFi? And how many NiFi nodes does your remote NiFi have? I've encountered the same error message when I conducted a test using hundreds of S2S client connecting to a single NiFi node. It happened in a situation like followings: 1. A S2S