[ 
https://issues.apache.org/jira/browse/NIFI-11627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779640#comment-17779640
 ] 

David Handermann commented on NIFI-11627:
-----------------------------------------

[~dstiegli1] implementing the {{SchemaRegistry}} interface would be useful, but 
the NiFi RecordSchema lacks certain features that JSON Schema provides. So for 
this particular Jira issue, that would not address the use case. Supporting 
more JSON Schema features would definitely be useful, and that is a related 
question.

> Add Dynamic Schema References to ValidateJSON Processor
> -------------------------------------------------------
>
>                 Key: NIFI-11627
>                 URL: https://issues.apache.org/jira/browse/NIFI-11627
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.19.1
>            Reporter: Chuck Tilly
>            Assignee: Daniel Stieglitz
>            Priority: Major
>
> For the ValidateJSON processor, add support for flowfile attribute references 
> that will allow for a JSON schema located in the Parameter Contexts, to be 
> referenced dynamically based on a flowfile attribute. e.g. 
> {code:java}
> #{${schema.name}} {code}
>  
> The benefits of adding support for attribute references are significant.  
> Adding this capability will allow a single processor to be used for all JSON 
> schema validation.  Unfortunately, the current version of this processor 
> requires a dedicated processor for every schema, i.e. 12 schemas requires 12 
> ValidateJSON processors.  This is very laborious to construct and maintain, 
> and resource expensive.  
> ValidateJSON processor (https://issues.apache.org/jira/browse/NIFI-7392)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to