[
https://issues.apache.org/jira/browse/NIFI-9072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434973#comment-17434973
]
Mark Payne commented on NIFI-9072:
----------------------------------
I'm not sure that I agree this should be supported. Attributes are intended to
always be very small - like a couple hundred characters or less. It is very
much an anti-pattern to put things like XML and JSON in attributes, and it’s
really something that we should not encourage. Creating large attributes can
have a hugely detrimental effect on nifi performance (due to having to write
lots of attributes to both the flowfile repository and provenance repository,
plus using up available heap, and it drastically slows down startup times) as
well as node stability and cluster stability (due to garbage collection, out of
memory errors, heap exhaustion, etc.)
> 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)
