[
https://issues.apache.org/jira/browse/NIFI-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-12733:
----------------------------------
Fix Version/s: (was: 1.26.0)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> 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
>
> Time Spent: 40m
> 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)
