[ 
https://issues.apache.org/jira/browse/NIFI-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julien G. updated NIFI-12733:
-----------------------------
    Description: 
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. 

  was:
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 {{name}} but 2 different 
{{groupId}}.

So the {{groupId}} should be optionnal and settable with the {{Schema Branch}} 
property. 


> Make Apicurio's groupId optional and configurable and use artifactId instead 
> of name
> ------------------------------------------------------------------------------------
>
>                 Key: NIFI-12733
>                 URL: https://issues.apache.org/jira/browse/NIFI-12733
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Julien G.
>            Priority: Major
>
> 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)

Reply via email to