<extensionManifest><groupId>org.apache.nifi</groupId><artifactId>nifi-network-processors-nar</artifactId><version>2.0.0-M4</version><parentNar><groupId>org.apache.nifi</groupId><artifactId>nifi-standard-shared-nar</artifactId><version>2.0.0-M4</version></parentNar><systemApiVersion>2.0.0-M4</systemApiVersion><buildInfo><tag>nifi-2.0.0-M4-RC1</tag><branch>UNKNOWN</branch><revision>19c5be0</revision></buildInfo><extensions><extension><name>org.apache.nifi.processors.network.ParseNetflowv5</name><type>PROCESSOR</type><description>Parses netflowv5 byte ingest and add to NiFi flowfile as attributes or JSON content.</description><tags><tag>network</tag><tag>netflow</tag><tag>attributes</tag><tag>datagram</tag><tag>v5</tag><tag>packet</tag><tag>byte</tag></tags><properties><property><name>FIELDS_DESTINATION</name><displayName>Parsed fields destination</displayName><description>Indicates whether the results of the parser are written to the FlowFile content or a FlowFile attribute; if using flowfile-attribute, fields will be populated as attributes. If set to flowfile-content, the netflowv5 field will be converted into a flat JSON object.</description><defaultValue>flowfile-content</defaultValue><allowableValues><allowableValue><displayName>flowfile-content</displayName><value>flowfile-content</value><description>Parsed data routes as flowfile JSON content</description></allowableValue><allowableValue><displayName>flowfile-attribute</displayName><value>flowfile-attribute</value><description>Parsed data routes as flowfile attributes</description></allowableValue></allowableValues><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property></properties><relationships><relationship><name>success</name><description>Any FlowFile that is successfully parsed as a netflowv5 data will be transferred to this Relationship.</description><autoTerminated>false</autoTerminated></relationship><relationship><name>failure</name><description>Any FlowFile that could not be parsed as a netflowv5 message will be transferred to this Relationship without any attributes being added</description><autoTerminated>false</autoTerminated></relationship><relationship><name>original</name><description>The original raw content</description><autoTerminated>false</autoTerminated></relationship></relationships><readsAttributes><readsAttribute><name>udp.port</name><description>Optionally read if packets are received from UDP datagrams.</description></readsAttribute></readsAttributes><writesAttributes><writesAttribute><name>netflowv5.header.*</name><description>The key and value generated by the parsing of the header fields.</description></writesAttribute><writesAttribute><name>netflowv5.record.*</name><description>The key and value generated by the parsing of the record fields.</description></writesAttribute></writesAttributes><supportsBatching>true</supportsBatching><sideEffectFree>true</sideEffectFree><inputRequirement>INPUT_REQUIRED</inputRequirement></extension><extension><name>org.apache.nifi.processors.network.pcap.SplitPCAP</name><type>PROCESSOR</type><description>Splits one pcap file into multiple pcap files based on a maximum size.</description><tags><tag>PCAP</tag><tag>Splitter</tag><tag>Network</tag><tag>Packet</tag><tag>Capture</tag><tag>Wireshark</tag><tag>TShark</tag><tag>TcpDump</tag><tag>WinDump</tag><tag>sniffers</tag></tags><properties><property><name>PCAP Max Size</name><displayName>PCAP Max Size</displayName><description>Maximum size of each output PCAP file. PCAP packets larger than the configured size result in routing FlowFiles to the failure relationship.</description><defaultValue>1 MB</defaultValue><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property></properties><relationships><relationship><name>original</name><description>The original FlowFile that was split into segments. If the FlowFile fails processing, nothing will be sent to this relationship</description><autoTerminated>false</autoTerminated></relationship><relationship><name>failure</name><description>If a FlowFile cannot be transformed from the configured input format to the configured output format, the unchanged FlowFile will be routed to this relationship.</description><autoTerminated>false</autoTerminated></relationship><relationship><name>split</name><description>The individual PCAP 'segments' of the original PCAP FlowFile will be routed to this relationship.</description><autoTerminated>false</autoTerminated></relationship></relationships><writesAttributes><writesAttribute><name>error.reason</name><description>The reason the FlowFile was sent to the failure relationship.</description></writesAttribute><writesAttribute><name>fragment.identifier</name><description>All split PCAP FlowFiles produced from the same parent PCAP FlowFile will have the same randomly generated UUID added for this attribute</description></writesAttribute><writesAttribute><name>fragment.index</name><description>A one-up number that indicates the ordering of the split PCAP FlowFiles that were created from a single parent PCAP FlowFile</description></writesAttribute><writesAttribute><name>fragment.count</name><description>The number of split PCAP FlowFiles generated from the parent PCAP FlowFile</description></writesAttribute><writesAttribute><name>segment.original.filename</name><description>The filename of the parent PCAP FlowFile</description></writesAttribute></writesAttributes><sideEffectFree>true</sideEffectFree><inputRequirement>INPUT_REQUIRED</inputRequirement></extension></extensions></extensionManifest>