Lars,
If start a processor and then stop it, the thread does not get killed.
The processor will continue to run until that thread completes its job. The
processor will then remain stopped and not execute again until manually
started again.
Matt
On Jan 18, 2016 10:54 AM, "Joe Percivall" wrote:
Joe and Lars,
I created a Jira ticket for this issue:
https://issues.apache.org/jira/browse/NIFI-1407
We can continue the conversation there instead two different email threads.
Joe - - - - - - Joseph Percivalllinkedin.com/in/Percivalle:
joeperciv...@yahoo.com
On Sunday, January 10, 2016 4
Joe,
thanks for the welcome and the (really quick) reply.
My use-case (and again I may use NiFi for things it wasn't intended to) is
for a one-time/initial-import scenario. I have a Processor that I'd like to
start that then calls a Web service and pages through all results creating
FlowFiles and
Lars,
First, welcome to NiFi.
So you'll initiate the flow from NiFi through some manual trigger and
that part makes sense/sounds straightforward. But then the question
is 'once the flow is done' I'd like it to shut down. What are the
processors/things that begin the flow? We've recently had so
Hi,
I'm just getting started with Nifi and understand that I probably still
have some misconceptions :)
For various reasons I'd love to use NiFi for one-time actions/processors
which I'd like to trigger as needed from the UI. I've seen the various
scheduling strategies and the closest I've come i