https://bz.apache.org/bugzilla/show_bug.cgi?id=65681
Felix Schumacher <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #38086|0 |1 is obsolete| | --- Comment #5 from Felix Schumacher <[email protected]> --- Created attachment 38091 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38091&action=edit Set default value when a null value is found by the JSON path expression I added test cases for the new behaviour. I am not sure, whether the handling of multiple results is correct or intended. Consider the structure '[{"c": null}, {"c": "abc"}]' and the path '$[*].c' with a default value of "NONE". JSON Path will lead to a result of '[null, "abc"]' which we will enhance to '["NONE", "abc"]'. (That sounds valid) But, what if the user intended to give a default value for a complete absent result? Like using an expression '$.listOfValues' on the above structure and an expected default value '[1, 2, 3]'? In that case the new implementation would yield unexpected results. What are your opinions on this? -- You are receiving this mail because: You are the assignee for the bug.
