Hello Apache NiFi Community
The release of Apache NiFi 0.4.1 passes with
5 +1 (binding) votes
2 +1 (non-binding) votes
0 -1 votes
This release is an incremental/bug fix release building on the many
improvements of 0.4.0.
Here is the community vote thread:
http://s.apache.org/vote041
To toss in another instance where this change can act against valid
use-cases, consider any instance where you might want to use the Expression
Language to cause one of these 'source' processors to not only run on a
'trigger', but also run more dynamically. Previously, you could potentially
use
Aha, that makes sense. Thanks for the explanation! I do agree that it could
be useful to have control over when those types of processors execute.
Thanks Richard.
I will test it tomorrow.
Sumo
Sent from my iPad
> On Dec 21, 2015, at 11:25 PM, Richard Miskin wrote:
>
> Hi Sumanth,
>
> I think you need to assign the return of putAllAttributes() to ff. A new
> FlowFile is created as part of that call.
>
> Cheers,
>
This sounds great. Profile activation makes sense. I like the test app
idea as well, perhaps we could eventually capture some data from that such
as CPU time, memory usage, architecture, etc. to better gather a set of
benchmarks and expectations for various components.
Would it make sense to
Thank you very much. That solved the problem. I changed from the default
blank value to the name of the machine on the NCM but I still got errors.
When I filled in the value on the node machine it started working.
--
View this message in context:
I've updated the migration guidance to better highlight this change:
https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
It is important to note that GetFile has never been driven by input
flow files. The desire for that totally makes sense and that is what
the ListFile/FetchFile