You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The order of field names and field values doesn't match for SCAN query with JSON output. Try the following in tile38-cli
>SET fleet truck1 FIELD speed 90 FIELD age 21 POINT 33.5123 -112.2693
>SCAN fleet match truck*
{"ok":true,"fields":["age","speed"],"objects":[{"id":"truck1","object":{"type":"Point","coordinates":[-112.2693,33.5123]},"fields":[90,21]}],"count":1,"cursor":0,"elapsed":"170.4µs"}
I found the issue and fixed it. It seems to have occurred specifically with JSON output. RESP output and other retrieval commands did not encounter this problem.
This commit fixes an issue that happens when running SCAN on a
collection that has objects with fields, causing field values
to be mismatched with their respective keys.
This only occured with json output, and is a regression from #534.
Fixes#569
The order of field names and field values doesn't match for
SCAN
query with JSON output. Try the following intile38-cli
Reformated JSON output is shown below:
As shown above, the field names order is
["age", "speed"]
and the field values order is[90, 21]
.Tried both for version 1.21.1 and
master
branch.The text was updated successfully, but these errors were encountered: