Re: [External] Re: Having a processor wait for all inputs

Hi, Thanks Andy/Lee, will take a look. — Mike From: Lee Laim > Reply-To: "users@nifi.apache.org" > Date: Thursday, March 16, 2017 at 10:01 AM To:

Re: Having a processor wait for all inputs

Hi Mike, Depending on the specifics of the inputs (source, format, correlating attributes, etc.) it sounds like you have a few good options to achieve this. 1. MergeContent [1] — This processor is very old (read: stable & widely-used, not legacy) and is used to merge content from multiple

Having a processor wait for all inputs

Hi, I’ve just started taking a look at Nifi as it seems perfect for a project I’m working on right now. The one thing I’m trying to solve is this – I have a process (say a batch job or similar) that I want to invoke, only once all the inputs have arrived ( a simple dependency graph ). i.e. I

Re: RuleEngine Processor

Uwe, I will do my best to look at this but it will probably be next week. It seems very interesting and my only excuse is being swamped by other things. Thank you for sharing this, hopefully others in the community will give it a go as well. Regards, Matt > On Mar 15, 2017, at 6:12 PM, Uwe

RuleEngine Processor

Hello, I have worked quite a bit on my RuleEngine processor and would appreciate, if somebody takes some time to try it and to look at the source code and give me some feedback. You can download it at: https://github.com/uwegeercken/nifi_processors It is my first bundle of processors, so I

Re: Nifi 1.1.0 cluster on Docker Swarm

Great. I have an overlay network listed in docker-compose, sure. I want to narrow down the issue, so if the Nifi configuration is working, that's already a big step. Thank you for your time. On Wed, Mar 15, 2017 at 3:28 PM, Jeremy Dyer wrote: > Raf - Ok so good news and bad

Re: Nifi 1.1.0 cluster on Docker Swarm

Raf - Ok so good news and bad news. Good news its working for me. Bad news its working for me =) Here is the complete list of things that I changed. Hopefully this can at least really help narrow down what is causing the issue. - I ran on a single machine. All that was available to me while at

Re: Upgrading NiFi, preserving process groups

Jim, Yes - if you copy over the flow.xml.gz then that's all that you should need to do in order to preserve your flow. If you are running NiFi 0.x though you will also want to copy over your conf/templates directory. In the 1.x baseline, Templates are included in the flow.xml also. Thanks

Re: Nifi 1.1.0 cluster on Docker Swarm

Awesome, we wrap https://github.com/mkobit/docker-nifi to add some custom processors: Tx FROM mkobit/nifi:1.1.0-openjdk-8COPY . /opt/nifi/WORKDIR /opt/nifi/RUN cp dependencies/*.nar $NIFI_HOME/libEXPOSE 8080CMD tail -F ${NIFI_HOME}/logs/nifi-app.log & ${NIFI_HOME}/bin/nifi.sh run On Wed,

Upgrading NiFi, preserving process groups

Good morning. Are there any specific steps I need to take to ensure I preserve all my Process Groups when I upgrade my version of NiFi? Does the step by which I save and copy flow.xml.gz into the conf subdirectory of the new version ensure that my Process Groups transfer to the upgraded version