[
https://issues.apache.org/jira/browse/NIFI-10589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17624158#comment-17624158
]
Nathan Gough commented on NIFI-10589:
-------------------------------------
This is interesting, I tested this in NiFi/NiFi Registry on NiFi 1.17.0 and on
the main branch (unreleased NiFI 1.19.0) and do not see the issue. The retry
relationships are being stored and retrieved correctly when I follow the
sequence of operations shown in the attached screenshots.
I am not using Docker for either NiFi or NiFi Registry which I don't suspect
would be the cause, but is there possibly some other conditions that could be
causing the issue?
> Retry Relationships no sending to nifi-registry on commit
> ---------------------------------------------------------
>
> Key: NIFI-10589
> URL: https://issues.apache.org/jira/browse/NIFI-10589
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, NiFi Registry
> Affects Versions: 1.17.0, 1.18.0
> Environment: docker
> Reporter: Yohany Flores
> Priority: Critical
> Attachments: ksnip_20221004-103903.png, ksnip_20221004-103959.png,
> ksnip_20221004-104021.png, ksnip_20221004-104036.png,
> ksnip_20221004-104047.png, ksnip_20221004-104101.png,
> ksnip_20221004-104112.png, ksnip_20221004-104124.png,
> ksnip_20221004-104136.png, ksnip_20221004-104150.png,
> ksnip_20221004-104202.png
>
>
> When configuring in any processor the RelationShips Tab with retry
> information, it is not transmitted to the nifi-registry.
> A simple Process Group, which is configured with Retry Relationship, is sent
> to the nifi-registry. When the process group is imported from the
> nifi-registry the retry information is not present in the new process group.
> I am using
> nifi-registry 1.17
> nifi 1.17
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
