Lexing error in v2 API

[RJKeevil]

Describe the bug

Hello, i'm in the process of moving to the v2 apis to make use of namespaces. In doing so I am getting lexing errors in queries that previously worked (and still succeed in ratel). I think the json parsing has differences.

To Reproduce

Take the following json from one of our test cases:
{"set":[{"uid":"_:R_1","dgraph.type":["Record","Agg1Record"],"Record.type":"agg1","Record.updateTS":"2025-06-24T08:59:24.894369149Z","Record.identifier":"agg1:BASIC1","Record.dateTime":"2017-02-20T12:00:00Z","Record.raw":"{\"doc\":\"Aggregation Document 1\"}","Record.hash":"3bpk0kclixpif","Record.individualEntity":[{"uid":"_:E_1_1","dgraph.type":["Entity","IndividualEntity"],"IndividualEntity.updateTS":"2025-06-24T08:59:24.894369149Z","IndividualEntity.identifier":"agg1:BASIC1:1","IndividualEntity.full":true,"IndividualEntity.displayName":"Aggregate 1 High","IndividualEntity.nameNormalised":"aggregate 1 high","IndividualEntity.customNameEmbedding":"22ejj75adgi22","IndividualEntity.nameParsed":"{\"initials\":[\"a\",\"h\"],\"raw\":\"aggregate 1 high\",\"words\":[\"aggregate\",\"1\",\"high\"]}","IndividualEntity.graphEmbedding":"te1kunpmfqr8","IndividualEntity.name":"Aggregate 1 High","IndividualEntity.individualID":1}]}]}

In Ratel I get Message: Done

When passing the same string to ns.Client.RunDQL(ctx, ns.Name, mutation) I get:
at line 1 column 1: Unexpected character while lexing DQL: U+0022 '\"'"

Expected behavior

The structure of a set request matched in ratel and v2 api

Environment

• OS: amazonlinux
• Language Go
• Version latest master

[linear]

DGR-892 Lexing error in v2 API

[matthewmcneely]

Ratel uses the /mutate endpoint which takes this type of json-formatted payload. When you say "previously worked", what lang/library/endpoint were you using?

[RJKeevil]

I was using dgo with the v1 apis over grpc, via SetJson. All my set commands are pretty much arrays of json documents, it would be great if I could also use that in v2 as there would be a lot to convert otherwise! Plus im not sure the blanknode references work the same way in RDF? It may be i can already use json in v2 but im reading the docs wrong btw.

[RJKeevil]

E.g. this doc page implies json mutations should work as I am using them https://docs.hypermode.com/dgraph/dql/json

[matthewmcneely]

So, using SetJson like this:

dgo/example_set_object_test.go

Line 122 in 4a519e5

mu.SetJson = pb

If so, note that the "set" field is not present, just the json encoded object. Hopefully, this will be moot when/if we get namespace support for v25. I'm guessing your existing code uses dg.NewTxn() as in the example_set_object_test.go file.

[RJKeevil]

Hi @matthewmcneely, that is that pattern i was using previously in the v1 apis. However I dont think that supports the namespace functionality, which is why I was looking for an equivalent v2 function, i.e. using RunDQL with a set of a json array. So you think instead the SetJson function will be modified to include namespaces? i.e. via your PR?

[matthewmcneely]

Right, if that PR gets merged, instead of txn := client.NewTxn(), you'd use txn := client.NewTxnInNamespace("foo")

[RJKeevil]

Cool. I still think this Lexing issue needs fixing however, as it will confuse a lot of people that the examples in first page of the DQL docs (JSON data format) doesnt run in the RunDQL function?

I might try a PR to make the examples from the docs unit tests.

[RJKeevil]

OK ive updated the tests in a draft PR at #267, it shows the failure with a basic example and references the docs that claims this should be working. Hope this helps!