David Handermann created NIFI-14846:
---------------------------------------
Summary: Deprecate ParseNetflowv5, GeohashRecord, and
CreateHadoopSequenceFile for Removal
Key: NIFI-14846
URL: https://issues.apache.org/jira/browse/NIFI-14846
Project: Apache NiFi
Issue Type: Improvement
Reporter: David Handermann
Assignee: David Handermann
Several Processors should be deprecated for removal based on current
implementation and future support priorities.
*ParseNetflowv5*
The {{ParseNetflowv5}} Processor should be removed because the current
implementation relies on receiving Netflow V5 binary packets and also expects
to having the receiving port number in a FlowFile attribute, presumably from
{{ListenUDP}}. Future support for Netflow should consider additional protocol
versions, and implement support as a Listen Processor. Additional
considerations include using a Record Writer, instead of FlowFile attributes or
JSON content, to make Netflow packet handling more flexible for general use
cases.
*GeohashRecord*
The {{GeohashRecord}} Processor has not received any substantive changes since
the initial introduction in 2021. It also includes multiple output strategies
that introduce additional complexity. As it is a less common feature,
continuing maintenance within the project should be reconsidered.
*CreateHadoopSequenceFile*
The {{CreateHadoopSequenceFile}} Processor should be removed because it implies
tight coupling between FlowFile handling and storage structure. Supported
formats include the Apache NiFi FlowFile Stream V3, which as an internal format
not suited for persistence in external systems such as Hadoop. The Tar and Zip
options provide greater flexibility, but also require a specific knowledge of
the packed FlowFile content stored. As this Processor has not received notable
maintenance in a number of years, and other file formats provide more
generalized storage solutions, this Processor should be deprecated for removal.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
