[ 
https://issues.apache.org/jira/browse/NIFI-11156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686636#comment-17686636
 ] 

David Handermann commented on NIFI-11156:
-----------------------------------------

Thanks for describing this issue [~bilalb].

Changes to the content of the {{validatexml.invalid.error}} attribute were 
introduced as a result of generalized XML processing improvements in NIFI-9901.

The generalized "Validation failed" message comes from the 
{{ProcessingException}} thrown in {{StandardSchemaValidator}}. To provide more 
details in the error attribute, an ideal solution would walk through the 
exception causes and build up the string of messages. That should allow 
{{StandardSchemaValidator}} to remain unchanged, and also provide the expected 
details in this error attribute value.

> ValidateXml Processor - validatexml.invalid.error = Validation failed
> ---------------------------------------------------------------------
>
>                 Key: NIFI-11156
>                 URL: https://issues.apache.org/jira/browse/NIFI-11156
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.19.1
>         Environment: CentOS 7.5, RedHat 7.9
> Temurin - 11.0.17+8
>            Reporter: Bilal
>            Priority: Minor
>
> _NiFi_ environment was upgraded from 1.15.1 to 1.19.1. The following 
> situation has occurred with the _ValidateXml_ processor:
> _ValidateXml_ processor works correctly on 1.15.1 and 
> _validatexml.invalid.error_ attribute gives an detail information about the 
> error.
> _ValidateXml_ processor works on 1.19.1 but _validatexml.invalid.error_ 
> attribute does not give an detail information about the _error. 
> validatexml.invalid.error_ attriubute only contains “{_}Validation failed{_}” 
> text.
> Similar problem was talked in cloudera community and Eduu said that:
> ===========
> Hi 
> [@ChuckE|https://community.cloudera.com/t5/user/viewprofilepage/user-id/98065]
>  using NiFi 1.15.2 seems to add the error detail in the 
> "validatexml.invalid.error" attribute.
> For example --> "cvc-minLength-valid: Value '' with length = '0' is not 
> facet-valid with respect to minLength '1' for type 'HotelCode"
> This seems to be an issue starting from NiFi 1.16.3, maybe a bug?
> You can use NiFi 1.15.2 or custom code as 
> [@SAMSAL|https://community.cloudera.com/t5/user/viewprofilepage/user-id/80381]
>  suggested.
> ===========
> Ref: [How to get the reason for invalid 
> XML|[https://community.cloudera.com/t5/Support-Questions/How-to-get-the-reason-for-invalid-XML/m-p/348767/highlight/true#M235443]]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to