You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2019/07/24 12:49:30 UTC

[Bug 63605] New: JSON Exractor is not retrieving null arrays and its associated elements with conditions

https://bz.apache.org/bugzilla/show_bug.cgi?id=63605

            Bug ID: 63605
           Summary: JSON Exractor is not retrieving null arrays and its
                    associated elements with conditions
           Product: JMeter
           Version: 4.0
          Hardware: PC
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: kandasamy.suryaprakashn@kohls.com
  Target Milestone: JMETER_5.2

Hi Team,

We have observed that in jsonpath.com we tried a request and queried a
condition to identify the json attributes of the array elements which is null
and it successfully retrieved the values. The same we have tried in jmeter but
its not working

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 63605] JSON Exractor is not retrieving null arrays and its associated elements with conditions

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63605

--- Comment #5 from kandasurya912@gmail.com ---
Thanks Felix Thanks a lot I got it. It is working as expected

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 63605] JSON Exractor is not retrieving null arrays and its associated elements with conditions

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63605

Felix Schumacher <fe...@internetallee.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 OS|                            |All

--- Comment #1 from Felix Schumacher <fe...@internetallee.de> ---
Please supply a minimal test case that shows the behaviour. I did not
understand, what data you were using not what expression you used.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 63605] JSON Exractor is not retrieving null arrays and its associated elements with conditions

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63605

--- Comment #2 from kandasurya912@gmail.com ---
(In reply to Felix Schumacher from comment #1)
> Please supply a minimal test case that shows the behaviour. I did not
> understand, what data you were using not what expression you used.

Hi Felix,

Actually my json looks like below.

[{
                "temperature": 54.4461,
                "area": "US",
                "listeners": [],
                "province": "california"
        },
        {
                "temperature": 59.4461,
                "area": "US",
                "listeners": [],
                "province": "ohaiio"
        },
        {
                "temperature": 51.4461,
                "area": "US",
                "listeners": [],
                "province": "florida"
        },
        {
                "temperature": 54.4461,
                "area": "US",
                "listeners": [{
                        "area": 1,
                        "areaCode": 3,
                        "places": 780
                }],
                "province": "california"
        }
]

My JOSN Expression:

$.[?(@.listeners == "")].temperature

My requiremnet is need to take the values where listerners array is null. I
checked the above in jsonpath.com and it came successful. Please find the snap

The abve expression is not working in jmeter. Please look into this. This is
blocking my entire activities

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 63605] JSON Exractor is not retrieving null arrays and its associated elements with conditions

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63605

Felix Schumacher <fe...@internetallee.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID
   Target Milestone|JMETER_5.2                  |---
           Severity|critical                    |minor

--- Comment #4 from Felix Schumacher <fe...@internetallee.de> ---
JMeter uses Jayway as its jsonpath implememtation. JSONPath seems to have no
hard specification. The implementations might differ. Look at
https://jsonpath.herokuapp.com/ for testing your data and expression.

I think this question should have been asked on the users mailing list and
while it might be critical for you, it is definitely not critical as a
(possible) bug in JMeter.

With a minimal test I meant a jmx file showing the json data and the
expression, not a word document.

You might want to try  $[?(@.listeners.length() == 0)]

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 63605] JSON Exractor is not retrieving null arrays and its associated elements with conditions

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63605

kandasurya912@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 63605] JSON Exractor is not retrieving null arrays and its associated elements with conditions

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63605

--- Comment #3 from kandasurya912@gmail.com ---
Created attachment 36683
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=36683&action=edit
Find the attachment for not working in jemeter

Tried in jmeter version till 5.1.1 its not working

-- 
You are receiving this mail because:
You are the assignee for the bug.