[
https://issues.apache.org/jira/browse/NIFI-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-5682.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> There are unexpected content from another distinct flow in the result.
> ----------------------------------------------------------------------
>
> Key: NIFI-5682
> URL: https://issues.apache.org/jira/browse/NIFI-5682
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.7.1
> Environment: CentOS
> Reporter: Artem Anokhin
> Priority: Critical
> Attachments: 91674-capture.png, 91675-capture.png, Capture.PNG,
> Capture.PNG
>
>
> We have a very strange situation in our NiFi flow. The problem is that the
> result was with an unexpectable content from flow files that existing in the
> distinct flow.
> 1. The flow above generates in the first GenerateFlowFile processor the next
> content:
> {code:java}
> <extract>
> <SNMPSCANNER>
> <line>
> <ip>127.0.0.1</ip>
> <port>10001</port>
> <protocol>udp</protocol>
> <address>udp:127.0.0.1/10001</address>
> <community>airos</community>
> <status>0</status>
> <sysName>sysName</sysName>
> </line>
> </SNMPSCANNER>
> </extract>
> {code}
> and it falls into the result of the below flow after our custom
> SnmpProcessor. How can it be? The above flow was turned off during the
> execution of below.
> 2. The GenerateFlowFile generates something like
> {code:java}
> munity": "airos",
> "snmpVersion": "V2c",
> "transportProtocol": "UDP"
> }{
> "address": "127.0.0.1/10001",
> "comm
> {code}
> rather than was specified in it:
> {code:java}
> {
> "address": "127.0.0.1/100010",
> "community": "airos",
> "snmpVersion": "V2c",
> "transportProtocol": "UDP"
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
