You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Julien G. (Jira)" <ji...@apache.org> on 2024/02/02 19:38:00 UTC
[jira] [Assigned] (NIFI-12733) Make Apicurio's groupId optional and configurable and use artifactId instead of name as key
[ https://issues.apache.org/jira/browse/NIFI-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julien G. reassigned NIFI-12733:
--------------------------------
Assignee: Julien G.
> 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
> Time Spent: 10m
> 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 name is required to be unique across the registry.
> So the {{groupId}} should be optionnal and settable with the {{Schema Branch}} property.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)