[ https://issues.apache.org/jira/browse/NIFI-11627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774947#comment-17774947 ]
Mark Payne commented on NIFI-11627: ----------------------------------- [~nwchuckster] yes, the approach that you mentioned there, which uses {{evaluateELString}} was an oversight that has since been patched. Anywhere that you're using that, you'll want to fix because in more recent versions that will fail. > 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)