@neters Correct, this button should only restart the required services, NOT the entire cluster.  The next screen should present more details before a final button to kick it off. ... View more

@mango @joseomjr  Currently DTLS not supported with ListenUDP. You certainly can build your own processor or work on a version of ListenUDP that includes the necessary code changes.  Additionally it may be worth taking a look at the new python native capability in NiFi 2.0.    ... View more

@ckumar is Correct.   For large volume ingestion into the receiving host, you need a maria db host that can handle 1000s of transactions per second.   Nifi can easily exceed default configurations for total connections.   With a well tuned highly available mariadb,  you can crank up execution time and concurrency on nifi and get 10,000s+ transactions per second. ... View more

@Hae I am not exactly sure of your settings or the issue with transactions, but I can share what is working for me.   In my CDP Public Cloud nifi flows i use some required settings to PublishKafka. SSL Context Service:Default NiFi SSL Context Service Security Protocol: SASL_SSL SASL Mechanism: PLAIN Username: CDP Workload User Name Password: CDP Workload User Password   Make sure you user has access to everything of course and you have set the workload password. Additionally, be patient on first processor run, sometimes takes minute or so of startup time to see SUCCESS.  Then give refresh on SMM to make sure the kafka topic is created and has the expected data.   ... View more

In regards to your nifi expression language.:    Test in a simple flow, and inspect the flowfile's attributes to insure topicName is correct.    Then take it to the kafka processor.  If you are not seeing the results of the expression, something isnt right, or the value doesnt except Expression Language.  Look at the (?) on any property to see what is accepted.   I suspect the expression language is invalid as well, so make sure you test and confirm the attribute is as expected before trying to use it deeper in your flow.   In regards to mapping.   What i suggest could be DistributedMapCache or even a flow that does a lookup against some other service.  With this concept you provide a mapping key value pairs that correspond to your consumer and producer topics.  When you lookup a key, For Example:  "alerts_Consumer_Topic_Name" the value would be "alerts_Producer_Topic_Name".   If this is stored outside of nifi, then these values can be managed and changed outside of the scope of the nifi flow.   Example flow with DistributeMapCache:   https://github.com/ds-steven-matison/NiFi-Templates/blob/main/DistributedCache_Demo.xml ... View more