-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CallProcedure deserialization is not working with Read-Only queries #25
Comments
Thanks for reporting this! I'll take a look at the issue and your pull request very soon. |
@Ivan-Gyoshev It just occurred to me 🤦♂️, would you mind trying the method The implementation is VERY similar to the pull request that you opened. |
Hey @tombatron , Do you mean using the already implemented method |
Yes. Also, could I get some sample data and a sample procedure to replicate for a test. I'd also like to check Jedis's RedisGraph support for the same issue since my goal here is to essentially replicate the "official" support. |
1 similar comment
Yes. Also, could I get some sample data and a sample procedure to replicate for a test. I'd also like to check Jedis's RedisGraph support for the same issue since my goal here is to essentially replicate the "official" support. |
Hello, Here is a little sample of how you can reproduce this issue: Connect to your master Redis graph ConnectionMultiplexer connectionMultiplexer = ConnectionMultiplexer.Connect("localhost:6379,abortConnect=false");
After you enter some sample data in your graph, you have to connect to your read-only replica and read this data.
` As I described above, when you execute the read-only query and have a result, in the process of deserializing the nodes in the result, the StackExchange.Redis driver is throwing an exception because the deserialization process internally is making |
@Ivan-Gyoshev Would you mind trying: https://www.nuget.org/packages/NRedisGraph/1.7.0-rc ? If that works for you I'll finalize my changes and publish version 1.7.0. |
Yes, I tested it now and it seems to work fine. :) |
Expanded support for "read only" queries. Closes #25
We are using a Redis graph read-only replica and performing read-only queries. In standard scenarios when the result is a specific value like a string or long there aren't any problems, but in the case when we are expecting nodes, the deserialization is calling inside it a 'GRAPH.QUERY' and the read-only replica which is only accepting 'GRAPH_RO.QUERY' is throwing an exception.
The full path to the method is ResultSet>RecordIterator>DeserializeScalar>DeserializeNode>_graphCache.GetLabel>_labels.GetCachedData>GetProcedureInfo>CallProcedure
The text was updated successfully, but these errors were encountered: