[
https://issues.apache.org/jira/browse/NIFI-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071380#comment-16071380
]
ASF GitHub Bot commented on NIFI-4099:
--------------------------------------
Github user lfrancke commented on the issue:
https://github.com/apache/nifi/pull/1941
@trkurc Thank you for taking the time for your thorough review!
I'll go through everything you raised separately and will amend the pull
request.
You are totally correct that I forgot about backwards compatibility. In
that case I would add deprecation notices to the affected methods instead so
they can be removed in a later version. I did a quick search just now but
didn't see a policy on this.
Assuming this makes the 1.4 release could the removal happen in 1.5 or does
it need to wait until 2.0 or do you have any other policy?
> SNMP processors cannot be restarted with SNMPv3 & security
> ----------------------------------------------------------
>
> Key: NIFI-4099
> URL: https://issues.apache.org/jira/browse/NIFI-4099
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.4.0
> Reporter: Lars Francke
> Assignee: Lars Francke
> Labels: snmp
>
> The SNMP processors currently fail when stopped & started again because
> snmpTarget is not set to null and only if it is are the user credentials
> added to the current USM/Engine.
> So what happens is that SNMP4j complains that there is no username.
> I'll provide a patch that fixes this.
> In addition I'd like to update SNMP4J from the version that's being used 1.x
> (from 2009) to 2.5.6 from 2017. And I'd love to also do a code cleanup run.
> I'd prefer to have it all in one patch (it still won't be large) but if
> really needed I can separate it out into three patches.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
