Skip to content
This repository has been archived by the owner on May 10, 2023. It is now read-only.

Results contain encoded fields #1

Open
serkanserttop opened this issue Aug 19, 2014 · 0 comments
Open

Results contain encoded fields #1

serkanserttop opened this issue Aug 19, 2014 · 0 comments

Comments

@serkanserttop
Copy link

Thanks for the driver Philip.
I am unsure if you ever ended up finishing it and used it in any way. I managed to get results returned while testing the "Graph of the Gods" example from Titan. Field keys and field values with ints are decoded correctly, but field values with strings return encoded results. For example I have:
{
"age": 5000,
"name": "anVwaXRlcg=="
},
{
"age": 4000,
"name": "cGx1dG8="
}

Aged 5000 must be "jupiter" and "pluto" has age 4000. Did you manage to fix this kind of issues?
There is also the longest discussion I have seen on github related to msgpack, msgpack/msgpack#128. I am wondering if that change is related, but reading it (only parts of it, it's very long!) suggests that the newer version potentially should solve the issue for strings at least. It is possible that we have to manually decode other types.

Let me know if you know how to fix the issue, and I could help come up with a fix. Are you still maintaining this repo? I could not find another working RexPro driver for golang, https://github.com/sqs/go-rexster-client is http based and https://github.com/linkomnia/rexgo did not work at all.

serkanserttop added a commit to serkanserttop/gorexpro that referenced this issue Aug 19, 2014
This fixes the issue raised by me @
philipsoutham#1
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant