Open iariasleon opened 8 years ago
In the version:
"version" : "1.0.0-next"
"git_hash" : "fee3d035442e78c1a2e19720f68bdeba083ca560",
And they respond the payload in plain text (description) instead of json object :
http code: 200 - OK
headers:
date: Mon, 02 May 2016 09:25:11 GMT
fiware-correlator: c4b591e6-1047-11e6-bb3f-005056a20feb
connection: Keep-Alive
content-type: application/json
content-length: 34
payload: lists only valid for == and != ops
cases:
| q | payload |
|------------------------------------------------------------|------------------------------------|
| my_time>=2016-04-05T14:10:00,00Z | lists only valid for == and != ops |
| my_time>=2016-04-05T14:10:00.,00L | lists only valid for == and != ops |
| my_time==2016-04-05T14:00:00.00Z,,2017-04-05T14:00:00.00Z | empty item in list |
| my_time==2016-04-05T14:00:00.00Z...2017-04-05T14:00:00.00Z | invalid range: types mixed |
In CB version:
"version" : "1.1.0-next",
"git_hash" : "301c258a9ef8f05cabdc276b7e21365e8f4d5913"
These cases respond correctly, with a json object and the description see table below
| q | description |
|------------------------------------------------------------|------------------------------------|
| my_time>=2016-04-05T14:10:00,00Z | lists only valid for == and != ops |
| my_time>=2016-04-05T14:10:00.,00L | lists only valid for == and != ops |
| my_time==2016-04-05T14:00:00.00Z,,2017-04-05T14:00:00.00Z | empty item in list |
| my_time==2016-04-05T14:00:00.00Z...2017-04-05T14:00:00.00Z | invalid range: types mixed |
But these case are responding 201 - OK
| q |
|------------------------------------------------------------|
| my_time<>2016-04-05T14:00:00.00Z |
| my_time>=2r16-04-05T14:00:00.00Z |
| my_time>=-04-05T14:00:00.00Z |
| my_time>=2016_04-05T14:00:00.00Z |
| my_time>=2016-64-05T14:00:00.00Z |
| my_time>=2016--05T14:00:00.00Z |
| my_time>=2016-r4-05T14:00:00.00Z |
| my_time>=2016-04-55T14:00:00.00Z |
| my_time>=2016-04-r5T14:00:00.00Z |
| my_time>=2016-04-T14:00:00.00Z |
| my_time>=2016-04-05K14:00:00.00Z |
| my_time>=2016-04-05T54:00:00.00Z |
| my_time>=2016-04-05Tr4:00:00.00Z |
| my_time>=2016-04-05T:00:00.00Z |
| my_time>=2016-04-05T14;00:00.00Z |
| my_time>=2016-04-05T14:r0:00.00Z |
| my_time>=2016-04-05T14:44:00.00Z |
| my_time>=2016-04-05T14::00.00Z |
| my_time>=2016-04-05T14:10-00.00Z |
| my_time>=2016-04-05T14:10:x0.00Z |
| my_time>=2016-04-05T14:10:0x.00Z |
| my_time>=2016-04-05T14:10:.00Z |
| my_time>=2016-04-05T14:10:00.h00Z |
| my_time>=2016-04-05T14:10:00.0h0Z |
Re-tested in the CB version. It issue still fails and returns 201-Created
"version" : "1.2.0-next",
"git_hash" : "d81dcf28e71d8d63dc0929ef7a6b73d7db47421b"
Re-tested in the CB version. It issue still fails and returns 201-Created
"version" : "1.5.0-next"
"git_hash" : "d943fb6827fdee0d7e89501c343dc252f6757f60"
in POST v2/subscriptions with "q" condition expression but with invalid date values (ISO8601)
dataset
subscription request
subscription response
mongo docs
expected response