JSON snap not working as expected

[dabalka]

JSON splitter last week was working correctly.
Pipeline was not edited, JSON format did not change, and yet Pipeline is crashing indicating error that JSON splitter is expecting list not an object. Before 17th of Feb it was working perfectly fine. was something changed in snap architecture?
“Failure: Json Splitter expects a list, Reason: Found an object of type class java.util.LinkedHashMap, Resolution: The path $.data needs to refer to a list in the incoming document”

[dabalka]

You see, I was right that snap is not working as it was before 🙂

[ptaylor]

There’s a regression in the snap for this undocumented behavior. My apologies. We’re fixing it.

To clarify: this regression was introduced in the 431patches19359 patch version, and also exists in main19844 (the Feb 2023 GA version) and in 432patches19918. I recommend rolling back to main18944 (the Nov 2022 GA version) until we deploy a new patch to fix this.

[dabalka]

Thank you for this information!
I thought I’m loosing my mind 🙂

[alchemiz]

Hi Sir Patrick, any updates when the patch fix will be available?

[dabalka]

I’ve seen that it is already working correctly as before because I had to reverse all changes :stuck_out_tongue_winking_eye: , so I assume this is already done. At least on PaaS… @ptaylor please confirm?