Re: Template not saving parameter context assignment

Parameter contexts were added after the use of templates was no longer recommended and substantially deprecated and NiFi Registry was selected as the managed flow definition version control and environment promotion system. There are future efforts to facilitate the export/import of flow segment

Template not saving parameter context assignment

Hi, I have a flow that uses parameter contexts. I understand that the parameter context definitions themselves are persisted to flow.xml.gz. However, when I save my flow as a template, delete the flow from the canvas, then add the template back onto a blank canvas, all of the processor context a

Re: Issue with Secured NiFi on kubernetes using Helm charts

Thanks a million Sushil finally was able to get it up and running(With SSL). You just made my day, even though it's night time now :). After the tweaks you suggested, it worked all fine. Thanks again, Atul On Mon, Jul 27, 2020 at 11:49 PM Atul Wankhade wrote: > That's awesome, sure will take a

Nifi 1.8 to 1.11.4 migration issue

Hi Team, I am facing a wired issue while doing migration from 1.8 to 1.11.4 I am bringing flow.xml.gz,user.xml,authorization.xml from a nifi cluster(1.8 version) to a newly created 1.11.4 version cluster. When i am starting the 1.11.4 cluster with this new files, i am getting node disconnected er

Re: DetectDuplicate Processor Doesn't Remove From Cache

Hi, I'm questioning my understanding of how the code is working. I did a screen shot while debugging and I'll attach it here. If you look at the values of 'now' and 'originalCachevalue entryTimeMS', how could this ever work? Contrast the value of cacheValue.entryTimeMS vs originalCacheValue.ent

Re: DetectDuplicate Processor Doesn't Remove From Cache

Hello, I’m not sure that I understand the concern. CacheValue.getEntryTimeMS() returns a Long (64-bit signed integer) value, which represents the timestamp of when the entry was added. Are you experiencing problems with events not being evicted and resulting in heap exhaustion, or is your concer

DetectDuplicate Processor Doesn't Remove From Cache

Hi, I've developed a test where I'm caching a flowfile using PutDistributedMapCache, then checking for entries using a DeleteDuplicate processor. I'm finding that the DeleteDuplicate is, in fact, finding the duplicate, but it's not removing it from the cache. The problem is the test in DeleteDupl