nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-5566) Bring HashContent inline with HashService and rename legacy components
Date Tue, 04 Sep 2018 01:58:00 GMT

    [ https://issues.apache.org/jira/browse/NIFI-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602539#comment-16602539
] 

ASF GitHub Bot commented on NIFI-5566:
--------------------------------------

Github user alopresto commented on the issue:

    https://github.com/apache/nifi/pull/2983
  
    I created two templates that should help with testing the new behavior and ensuring that
upgrading a flow that uses the old components doesn't break it. 
    
    * [Hash Components (Legacy)](https://gist.github.com/alopresto/80fcabb78be26a04b894721c4f382300)
    * [Hash Components (New)](https://gist.github.com/alopresto/93ed6907037dce8bf855c9cb4354ea9d)


> Bring HashContent inline with HashService and rename legacy components
> ----------------------------------------------------------------------
>
>                 Key: NIFI-5566
>                 URL: https://issues.apache.org/jira/browse/NIFI-5566
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.7.1
>            Reporter: Andy LoPresto
>            Assignee: Andy LoPresto
>            Priority: Major
>              Labels: backwards-compatibility, hash, security
>
> As documented in [NIFI-5147|https://issues.apache.org/jira/browse/NIFI-5147] and [PR
2980|https://github.com/apache/nifi/pull/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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message