[
https://issues.apache.org/jira/browse/NIFI-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886095#comment-17886095
]
ASF subversion and git services commented on NIFI-13812:
--------------------------------------------------------
Commit 74091e1540cd6d6a92db5ff9ac71c838d160cc9e in nifi's branch
refs/heads/main from Ferenc Erdei
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=74091e1540 ]
NIFI-13812 [MiNiFi][C2] Add component type into Agent Manifest Hash calculation
Signed-off-by: Ferenc Kis <[email protected]>
This closes #9320.
> [MiNiFi][C2] Agent Manifest Hash should be calculated using component types
> ---------------------------------------------------------------------------
>
> Key: NIFI-13812
> URL: https://issues.apache.org/jira/browse/NIFI-13812
> Project: Apache NiFi
> Issue Type: Improvement
> Components: C2, MiNiFi
> Affects Versions: 2.0.0-M4
> Reporter: Ferenc Erdei
> Assignee: Ferenc Erdei
> Priority: Minor
> Labels: c2, minifi-java
> Fix For: 2.0.0-M5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, Agent Manifest Hash that present in the Agent Heartbeat are
> calculated only using the bundle group-artifact-version.
> Issue with the above logics:
> In case of python extensions the group and artifact fields are static, and
> versions are determined using the processors' version. Dropping processors
> with the same versions into the extensions directory is not visible in the
> manifest hence C2 Servers may not detect that the Agent has new/changed
> processor capability.
> We should add each component types into the manifest hashing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
