New JSON facets response format cannot be unserialized back into client structures

[mehdiym]

What version of Dgraph are you using?

1.2.1

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

Query for UID facets, and then try to unmarshal them into a Go struct.

Expected behaviour and actual result.

Expected: Facet values properly set.
Actual: Zero values.

I realize the facets response format has recently changed, but I don't understand how I can now unserialize it into my data structures : facets are now independent objects attached to the parent node while my Go facet properties are defined into the child node.

In the go doc example, the result is not unserialized into a Person anymore but instead into a generic json.RawMessage: does it mean it is not possible anymore?

How can I get facets directly back into my data structures?

[mileung]

I think I am having the same issue as @mehdiym
https://www.youtube.com/watch?v=9dMvEoYY9_E
Correct me if I'm wrong, but in my video example, I think I read @facets(read) should be in the query result since it's clearly there when using pings @facets(read) { ... }. How can I get the facet result inside its corresponding node and not outside of it?

[MichelDiz]

@mileung the result is correct. This is the new facet's behavior.

[MichelDiz]

@mileung please, share you experience in this issue #4907

This issue New JSON facets response format cannot be unserialized back into client structures #4798 is related to the new behavior. Even if we support both behaviors, this issue must be fixed.

[ashish-goswami]

Hi all, we have discussed facets format internally and prepared one document with different possible formats. Please checks below discuss post and provide your feedback.
https://discuss.dgraph.io/t/facets-format-in-mutation-requests-and-query-responses/6416