[
https://issues.apache.org/jira/browse/NIFI-11627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780036#comment-17780036
]
David Handermann commented on NIFI-11627:
-----------------------------------------
[~dstiegli1] Yes, that is a limitation of the current design. This seems like a
case where a new interface may be necessary. Spending some additional time to
evaluate what elements of JSON Schema map to the existing RecordSchema, and
which do not, would be a good starting point.
One approach might involve a way to capture to additional aspects of JSON
Schema in a different interface. I am familiar with JSON Schema capabilities,
but I have not gone through a careful comparison against NiFi Record Schema to
recommend a particular approach thus far.
> 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)
