Github user bbende commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2820#discussion_r204390557
--- Diff:
nifi-nar-bundles/nifi-network-bundle/nifi-network-processors/src/main/resources/docs/org.apache.nifi.processors.network.ParseNetflowv5/additionalDetails.html
---
@@ -0,0 +1,74 @@
+<!DOCTYPE html>
+<html lang="en">
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version
2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+ http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+ -->
+<head>
+<meta charset="utf-8" />
+<title>Netflowv5Parser</title>
+<link rel="stylesheet" href="../../../../../css/component-usage.css"
+ type="text/css" />
+</head>
+
+<body>
+ <p>
+ Netflowv5Parser processor parses the ingress netflowv5 datagram
format
+ and transfers it either as flowfile attributes or JSON object.
+ Netflowv5 format has predefined schema named "template" for
parsing
+ the netflowv5 record. More information: <a
title="RFC-netflowv5"
+
href="https://www.cisco.com/c/en/us/td/docs/net_mgmt/netflow_collection_engine/3-6/user/guide/format.html";>RFC-netflowv5</a>
+ </p>
--- End diff --
I think something like what is in dataschema.txt is fine. If we think
people are going to use the record processors on the output, then it wouldn't
hurt to also have the Avro schema, but not totally necessary.
---
