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

Daniel Stieglitz commented on NIFI-11627:
-----------------------------------------

[~exceptionfactory] I would like to clarify I am not actually creating a 
SchemaRegistry. I am trying to integrate the use of one. As a result I need to 
use SchemaAccesStrategy which involves returning the schema in a RecordSchema 
object. Since the schema is now accessed via a  SchemaAccesStrategy I have had 
to make an anonymous  SchemaAccesStrategy  to encapsulate the current 
functionality of obtaining the JSON schema from a resource. That is where I 
stored the contents of the JSON schema in the text section of 
SimpleRecordSchema. I assume (but not tested just yet) that the various Schema 
Registry implementations return the actual text of the schema also. Hence I 
would like to take advantage of that and build the necessary JSON Schema object 
for validation. I have been able to reuse much of the code found in 
SchemaAccessUtils to accomplish the integration of a SchemaRegistry. Please let 
me know if there is still an issue with this design. Thanks!

> 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