Member since
05-20-2022
66
Posts
6
Kudos Received
6
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2278 | 07-17-2023 11:25 PM | |
| 2373 | 04-17-2023 02:29 PM | |
| 9069 | 02-15-2023 08:47 PM | |
| 1670 | 02-08-2023 06:02 PM | |
| 8465 | 10-17-2022 11:48 AM |
08-03-2022
10:13 AM
1 Kudo
I've since discovered a super easy way to resolve this. Simply using the XMLRecordSetWriter does EXACTLY what I was looking for.
... View more
08-02-2022
10:41 PM
1 Kudo
This seems like a good idea. I'll give this a try and test the performance against the XSLT transform. I've never used the JOLT processors before so this will be a good opportunity to experiment with one. Thanks for the idea.
... View more
08-01-2022
05:30 PM
Yes, I validate the incoming xml with a strongly typed xsd.
... View more
08-01-2022
07:26 AM
Thank you SAMSL for your response. In the interest of scalability I was trying to avoid performing text manipulations. I ultimately decided to go with an XSLT transform since this processor is optimized for performing these types of operations, making it more scalable. I wanted to verify there wasn't an option within the XMLReader that I was missing, but it seems not. On a side note, as an intellectual curiosity I also tried using the QueryRecord processor to see if I could select the outermost element in a query and slap wrapper text around it. But it seems there is no way to perform this task with an XMLReader because it can't discern the schema of the data, so "select * from flowfile" is the only thing that works apparently.
... View more
07-28-2022
11:13 PM
When using the XMLReader service, how do you retain the outermost parent element of an XML document so when I convert it to JSON I have the outermost element in the JSON version too? For example, given the following XML document how do I capture the "<a>" element rather than just the "<b>" element? <a> <b>45</b> </a> What I want: {"a": {"b":45}} What I get: {"b":45}
... View more
Labels:
- Labels:
-
Apache NiFi
07-27-2022
10:05 AM
That would be nice, but unfortunately v.1.16.x doesn't incorporate this feature and all you get is a generic message: "Validation Failed". In the end I just resorted to downloading the problem flowfile from the queue, and then used xmllint to run a validation, which gave me the answer instantly. But it would be really nice if the developers put the error message back into the "validatexml.invalid.error" attribute in v.1.16.x
... View more
05-25-2022
07:29 AM
All that attribute reports is "Validation failed". I need to know why it failed and at what line number in the flow file it failed. Is it possible to get this information?
... View more
05-24-2022
08:19 PM
When using the ValidateXML processor with an XSD, how do I capture the reason for the invalid XML so I can troubleshoot instances when the incoming XML is invalid? Unfortunately I don't have access to a validation tool in the environment where NiFi is running so I need the feedback from the ValidateXML processor. I appreciate the help.
... View more
Labels:
- Labels:
-
Apache NiFi
05-23-2022
07:11 AM
Yep! That is absolutely correct. Thanks for that. I spent more time trying to resolve this than I care to admit, because of my bias. Thanks for this @SAMSAL
... View more
- « Previous
- Next »