You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/12/27 00:58:00 UTC
[jira] [Commented] (NIFI-11627) Add JSON Schema Registry Service for ValidateJson Processor
[ https://issues.apache.org/jira/browse/NIFI-11627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800657#comment-17800657 ]
ASF subversion and git services commented on NIFI-11627:
--------------------------------------------------------
Commit a06fe5905cbbf92f04a7e470fdb7d6c39d02b3c9 in nifi's branch refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a06fe5905c ]
NIFI-11627 Corrected TestValidateJson exception evaluation
Signed-off-by: David Handermann <ex...@apache.org>
> Add JSON Schema Registry Service for 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
> Labels: backport-needed
> Fix For: 2.0.0
>
> Time Spent: 9h
> Remaining Estimate: 0h
>
> 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)