[NIFI-5566] Bring HashContent inline with HashService and rename legacy components

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.1
• Fix Version/s: 1.8.0
• Component/s: Extensions
• Labels: backwards-compatibility hash security
• Assignee: Andy LoPresto
• Reporter: Andy LoPresto
• Created: 01/Sep/18 00:13
• Updated: 18/Sep/18 00:15
• Resolved: 18/Sep/18 00:15

Description

As documented in NIFI-5147 and PR 2980, the HashAttribute processor and HashContent processor are lacking some features, do not offer consistent algorithms across platforms, etc.

I propose the following:

• Rename HashAttribute (which does not provide the service of calculating a hash over one or more attributes) to HashAttributeLegacy
• Renamed CalculateAttributeHash to HashAttribute to make semantic sense
• Rename HashContent to HashContentLegacy for users who need obscure digest algorithms which may or may not have been offered on their platform
• Implement a processor HashContent with similar semantics to the existing processor but with consistent algorithm offerings and using the common HashService offering

With the new component versioning features provided as part of the flow versioning behavior, silently disrupting existing flows which use these processors is no longer a concern. Rather, Any flow currently using the existing processors will either:

1. continue normal operation
1. require flow manager interaction and provide documentation about the change
1. migration notes and upgrade instructions will be provided

Issue Links

• is depended upon by: NIFI-5582 Integrate legacy behavior of HashAttribute into CryptographicHashAttribute
• links to: GitHub Pull Request #2983