Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Community Articles

Find and share helpful community-sourced technical articles.
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!
Labels (2)
avatar
Rising Star

After upgrading to CFM 2.1.5 SP1from an older version, PublishKafkaRecord_1_0 stops working with the below error:

 

PublishKafka_1_0[id=36f1cffe-503d-3181-a562-ae216b5616b5] Processing halted: yielding 
[1 sec] java.lang.IllegalArgumentException: SaslMechanism value [null] not found at
org.apache.nifi.kafka.shared.property.SaslMechanism.lambda$getSaslMechanism$1
(SaslMechanism.java:57) at java.base/java.util.Optional.orElseThrow(Optional.java:408)
at org.apache.nifi.kafka.shared.property.SaslMechanism.getSaslMechanism(SaslMechanism.
java:57) at org.apache.nifi.kafka.shared.login.DelegatingLoginConfigProvider.
getConfiguration(DelegatingLoginConfigProvider.java:51) at org.apache.nifi.kafka.
shared.property.provider.StandardKafkaPropertyProvider.setSecurityProperties
(StandardKafkaPropertyProvider.java:86) at org.apache.nifi.kafka.shared.property.
provider.StandardKafkaPropertyProvider.getProperties(StandardKafkaPropertyProvider.
java:75)

This happens due an improvement performed in NIFI-10866.

 

Resolution

You can switch to newer PublishKafkaRecord processor like PublishKafkaRecord_2_0 or PublishKafkaRecord_2_6, both of which successfully eliminate the issue and also provide newer features as compared to the older 1_0 processor.

 

1,141 Views
Version history
Last update:
‎04-20-2026 11:51 PM
Updated by: