Dgraph v20.03.0 Int64 type displayed incorrectly

[wshelly]

What version of Dgraph are you using?

v20.03.0

Have you tried reproducing the issue with the latest release?

Yes

What is the hardware spec (RAM, OS)?

 2.8 GHz Intel Core i7
 MacOS - Docker

Steps to reproduce the issue (command/config used to run Dgraph).

1: docker run --rm -it -p 8000:8000 -p 8080:8080 -p 9080:9080 dgraph/standalone:latest
2: http://localhost:8000
3: Mutate:
{ "set": [ { "mid": 1193880128115965952, "phone": "8612345678900" } ] }
4:Query
{ query (func: has(mid)){ mid phone } }

5: result:
{ "data": { "query": [ { "mid": 1193880128115966000, "phone": "8612345678900" } ] }, "extensions": { "server_latency": { "parsing_ns": 177233, "processing_ns": 13054937, "encoding_ns": 278975, "assign_timestamp_ns": 15853539, "total_ns": 29683405 }, "txn": { "start_ts": 9 }, "metrics": { "num_uids": { "mid": 1, "phone": 1 } } } }

mid (1193880128115965952) changed to 1193880128115966000

Expected behaviour and actual result.

"query": [ { "mid": 1193880128115965952, "phone": "8612345678900" } ]

[MichelDiz]

It's reproducible, but it looks like a duplicate of an old one I can't find (but I remember there is, but maybe it was related to float). But it has to do with these two I think. #2378 and #2377

in the screenshot I have the result from ratel and the RDF from the export. Which means that the original data wasn't modified. It is related to the parser.

[martinmr]

I checked the output and Dgraph does the right thing. The issue happens when Ratel parses the output. It interprets the number as a float just like Dgraph was doing before.

I'll close the issue and open a new one in ratel.