Yes, it makes sense. But it shouldn't be too short as well. For example I
easily have RouteOnAttribute relationships with 1000+ characters.
(currently around 4000 is the longest).
Raymond
Op do 1 aug. 2019 om 17:05 schreef Joe Witt :
> Peter,
>
> It certainly makes sense to prevent authorized us
There seems to be some work going on this here:
https://issues.apache.org/jira/browse/NIFI-4239.
On Thu, Aug 1, 2019 at 4:49 PM 18680246...@163.com <18680246...@163.com>
wrote:
>
> Hello
>
> I'm learning how to use nifi to solve problems in my work. nifi really
> facilitates my work. I built MySQ
Thanks for the advice. Grouping multiple flows into one process group and
embedding process-groups within process groups are options to get some
oversight. They are limited however.
1) If multiple workflows are grouped into one Process Groups then
a) You need to create different output ports
o
"a Flow Registry that can hold extensions and we can then make nifi 2.0
fundamentally about distributing nifi as a kernel (small as possible) and
all extensions come from a flow registry on demand. "
Nice! Great to hear NiFi as an extensible platform. I would see that the
NiFi Registry is linked t
