Re: [VOTE] Release Apache NiFi MiNiFi 0.3.0

There are some really cool new features in this release and I'm really looking forward to seeing NiFi + MiNiFi + Registry all working together. Thanks everyone for their hard work! I was able to verify the hashes and the normal build + contrib check work on OSX 10.12.5. Also, a simple S2S flow

Re: Unable to checkpoint FlowFile Repository (No space left on device)

Hi Michael, I checked the system available inodes by running df -i command and there're quite enough inodes in the system. I then removed all the files in all repository folders and restarted the system, I couldn't see the error again. I will continue to track the problem to see what's causing it,

NiFI 1.4.0 UI can't be displayed in an IFrame?

Hi, I tried to display NiFi 1.4.0 UI in an IFrame but it failed to load with error below: Refused to display 'https://172.16.0.33:8443/nifi/' in a frame because it set 'X-Frame-Options' to 'sameorigin'. Note: This setup works using NiFi 1.1.2. Kindly advise. Thanks, Virgil -- Sent from:

Re: About NIFI-3620: Multipart support in invokeHTTP.java

Multipart is just a set of related content types (multipart/form-data, multipart/mixed). InvokeHTTP doesn't care too much about content types, it just sends bytes verbatim from the flowfile payload. What should be considered is for an upstream processor to create the multipart payload in the

Nifi on Apache Mesos-DC/OS

Hi, Has anyone tried to deploy nifi on Mesos or DC/OS and is there a recommended nifi deployment architecture for mesos or DC/OS? Regards Anil

Re: Unable to checkpoint FlowFile Repository (No space left on device)

Greetings Ben, The "No space left on device" error can also be caused by running out of inodes on your device. You can check this with "df -i". -- Mike On Tue, Dec 12, 2017 at 1:36 AM, 尹文才 wrote: > sorry that I forgot to mention the environment that caused this problem,

Re: Adding user in NIFI-1.4.0

Hi Pallavi, You need to configure nifi for a secure access (https) so you can login to NiFi as a specific user. There is a nifi tls toolkit that you can download for a start to create certificates and keys for your nifi server as well as for a user.

RE: About NIFI-3620: Multipart support in invokeHTTP.java

Ciao Pierre, I can spend some hours tomorrow looking deep in the invokeHTTP implementation and figure out a way to properly support Multipart messages, then write back in the ML asking for feedback before implementing it. @Andre in case you have already some code or ideas I'll be glad to

Re: About NIFI-3620: Multipart support in invokeHTTP.java

Hey Damiano, Andre will correct me in case I'm wrong but he is not working on https://issues.apache.org/jira/browse/NIFI-3620 at the moment. If you want to give it a try, that would be more than appreciated. Pierre 2017-12-11 18:01 GMT+01:00 Joe Witt : > Hello > > Sounds