https://bz.apache.org/bugzilla/show_bug.cgi?id=65681
--- Comment #13 from eR@SeR <[email protected]> --- Hello, I did the testing of the new implementation and it seems to work for cases that I can think of. Others are welcome to do the same :) Note: If the Default value is left empty, null and empty values will be identical i.e. null will be empty too, but that should be intended behavior, I guess. The question is whether the same should be used for JSON JMESPath Extractor and all other extractors where possible, to have unique behavior? I used the following example to compare the behavior of JSON and JSON JMESPath Extractor: {"category_ids":[null,"",9615,9617]} json expr: $.category_ids[*] ---> match no: -1 ----> Default values: NF we have: JSONCategory_ids_1=NF JSONCategory_ids_2= JSONCategory_ids_3=9615 JSONCategory_ids_4=9617 JSONCategory_ids_matchNr=4 ====================================== but in JSON JMESPath Extractor: json jmes expr: category_ids[*] ---> match no: -1 ----> Default values: NF we have: JMESPathCategory_ids_1= JMESPathCategory_ids_2=9615 JMESPathCategory_ids_3=9617 JMESPathCategory_ids_matchNr=3 IMO, they should behave the same in JMeter, to have consistency among JSON extractors. Not only for this example, but in general. If that is not possible, as Felix pointed out, then provide the examples which produce different outputs in JSON extractors in the corresponding documentation. -- You are receiving this mail because: You are the assignee for the bug.
