[
https://issues.apache.org/jira/browse/NIFI-11784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851032#comment-17851032
]
Stephen Jeffrey Hindmarch commented on NIFI-11784:
--------------------------------------------------
[~huntes5] I think this ticket should be closed as the advice from [~markap14]
was the correct answer rather than a workaround. This is the approach described
in the documentation. However I am also looking at issues involving parsing
Windows Event XML. In your particular case the reason the WindowsEventLogReader
was failing is that it is not set up to parse the RenderingInfo tag, which I
believe is a missing feature and am about to raise a ticket for it. My
workaround has been to use a ReplaceText to drop the RenderingInfo tag, as it
does not contain any data of interest to me. Your use case may vary.
> XML to JSON conversion loses data (ConvertRecord processor - XMLReader and
> JSONRecordSetWriter)
> -----------------------------------------------------------------------------------------------
>
> Key: NIFI-11784
> URL: https://issues.apache.org/jira/browse/NIFI-11784
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.22.0
> Environment: Tested on Windows with ConsumeWindowsEventLog,
> particularly obvious (100% failure rate) on ForwardedEvents channel in a
> WEF/WEC setup
> Reporter: Sean Hunter
> Priority: Major
> Attachments: 735fcbc4-13ee-4b9e-bee0-91eb9084cb7e.xml,
> image-2023-07-06-14-42-46-700.png, image-2023-07-06-14-45-15-939.png,
> image-2023-07-06-15-04-04-992.png, image-2023-07-06-15-04-53-194.png
>
>
> Screenshot of event going into ConvertRecord processor in XML with valid data
> in SubjectUserName field (one example of data that's lost):
> !image-2023-07-06-14-42-46-700.png!
> Screenshot of the same flowfile once processed, showing that SubjectUserName
> field has lost information:
> !image-2023-07-06-14-45-15-939.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
