[
https://issues.apache.org/jira/browse/NIFI-9072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435044#comment-17435044
]
Mark Bean commented on NIFI-9072:
---------------------------------
I fully agree with your reservation to use large XML documents (or any large
data item) in attributes. However, I find it overly limiting to prevent
responsible usage only for fear it may be abused.
I still believe this ticket represents a viable new feature when used
appropriately. For example, upstream customers may be populating attributes (in
XML format) to indicate metadata for the document contained in the flowfile
contents. This does not require a large XML document.
I pushed a new commit to the PR to include some additional documentation which
discourages the use of large-valued attributes. See the processor description
as well as the System Resources Considerations section.
> Improvements to ValidateXML
> ----------------------------
>
> Key: NIFI-9072
> URL: https://issues.apache.org/jira/browse/NIFI-9072
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.14.0
> Reporter: Mark Bean
> Assignee: Mark Bean
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The ValidateXML processor can be improved by optionally allowing a flowfile
> attribute to be validated instead of only content. A new property, "XML
> Source Attribute" is added to the processor. When this property is not empty,
> it specifies the attribute name where the XML to be validated is located.
> This XML is the source for validation.
> In addition, sometimes an XML schema is not known and/or the user simply
> wants to validate the XML is well-formed. The existing property, "Schema
> File" should be optional. When it is not set, then only basic validation to
> ensure the XML is well-formed is performed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
