[
https://issues.apache.org/jira/browse/NIFI-11627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781509#comment-17781509
]
Daniel Stieglitz commented on NIFI-11627:
-----------------------------------------
[~exceptionfactory] I tried seeing whether I could map
com.networknt.schema.JsonSchema to the RecordSchema interface but I did not see
anything that stood out that could make that happen. Also I am not sure what
would the benefit of that be as the Json schema would have to be reconstituted
in order to instantiate a com.networknt.schema.JsonSchema for validation. In
the interim, I have chosen the second route and I have created a new
Controller Service interface. I have tried to start small and I have developed
an in memory registry much like the AvroSchemaRegistry except it stores Json
schemas. I have some more testing to do but I am hoping to push a PR soon.
> 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)
