Hi Louis,
Glad to hear that works.
There are two approaches I can think of, to accumulate and combine
multiple service results.
The goal is creating a single FlowFile containing all service call
results, right?
1. Use DistributedCache(DC) as a shared heap space
- Each part of flow calls
Bryan/Josef,
Just wanted to let you know that I just tested this with NiFi 1.8.0 and NiFi
Registry 0.3.0 and I experience the same behavior as Josef.
-Chad
> On Jan 8, 2019, at 12:58 PM, Bryan Bende wrote:
>
> I will keep trying, but I haven't been able to reproduce using NiFi
> 1.8.0 and
I will keep trying, but I haven't been able to reproduce using NiFi
1.8.0 and registry 0.2.0.
I must be missing something.
On Tue, Jan 8, 2019 at 11:50 AM wrote:
>
> I've tried it now on another secured cluster exactly like you did:
>
> 1) Create PG "A" and save to registry
> 2)
I've tried it now on another secured cluster exactly like you did:
1) Create PG "A" and save to registry
2) Import PG "A" from registry and rename to "B"
3) Add new processor (Execute Script) to original PG "A" and save to
registry
4) Change version on PG "B" to
Hi Bryan
In my case it happens all the time, doesn't matter what kind of change. On my
first test below I've changed a variable on a processor inside the PG and the
second time (a few seconds ago) I've added a connection to my "Execute Script"
processor. All the time my second PG with the new
Hi Josef,
That sounds like a possible bug. I think the PG name is supposed to
remain unchanged.
I wasn't able to reproduce this though... in step 5 when you change
the "abc" group, what type of change are you making?
I did the following...
1) Create PG "A" and save to registry
2) Import PG "A"
Hi guys
I’ve faced again an (at least for me) unexpected behavior of NiFi 1.8.0
together with NiFi Registry.
Following use case:
1. Create a process group with name “abc” and add some processors to the pg
2. Commit the pg to the NiFi registry
3. Create a new pg and import the pg from
