[
https://issues.apache.org/jira/browse/NIFI-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821674#comment-17821674
]
ASF subversion and git services commented on NIFI-12733:
--------------------------------------------------------
Commit ecea18f79655c0e34949d94609c8909aeb2d093e in nifi's branch
refs/heads/main from Juldrixx
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ecea18f796 ]
NIFI-12733 Make Apicurio's groupId optional and configurable and use artifactId
instead of name as key
Signed-off-by: Pierre Villard <[email protected]>
This closes #8351.
> Make Apicurio's groupId optional and configurable and use artifactId instead
> of name as key
> -------------------------------------------------------------------------------------------
>
> Key: NIFI-12733
> URL: https://issues.apache.org/jira/browse/NIFI-12733
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Julien G.
> Assignee: Julien G.
> Priority: Major
> Fix For: 2.0.0, 1.26.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In NiFi, when looking for a schema in Apicurio, it will extract the
> {{groupId}} to use it to retrieve the schema. But in fact, in Apicurio, the
> {{groupId}} is optional. So if the {{groupId}} is not set in Apicurio, it
> will fail to retrieve the schema. And 2 schema can have the same {{id}} but 2
> different {{groupId}}.
> And currently we are using the {{name}} of the schema to retrieve it but the
> key should be the {{id}} of the schema because the {{id}} is required to be
> unique across the registry but not the {{name}}.
> So the {{groupId}} should be optionnal and settable within the controller
> with a dedicated property.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
