-
Notifications
You must be signed in to change notification settings - Fork 116
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
Getting subtree encoded as JSON in one update message #20
Comments
Hi CoCumis, you should get an encoded subtree as per gNMI spec: which client and target are you using? Can you provide examples of the get and the response? |
Thanks for response. I am using docker image provided by faucet which you are mentioning in your README. For get request I use script provided in this docker image. Here is example:
I would expect it will send response with one update message which contains JSON encoded subtree. But instead I get this (just excerpt):
I also get the same result, if I try it with java client (generated from gnmi.proto). Is there something I had to configure in order to get whole subtree encoded as JSON instead of separate update message for each leaf? |
Should be fixed now. Please reopen if something is amiss. |
Hi, bugfix you provided fixes this problem only when the encoding is set to Please, can you reopen this issue? |
Thanks I have a potential fix here: https://github.com/samribeiro/gnxi/tree/gnmi |
Hi guys, I have question regarding encoding of data. According to gNMI specification, section 2.3.1, I assumed, that when I will send get request to target, with a path which does not point to leaf node, then in response message will be one notification with one update message which value will be JSON encoded subtree located under this path.
But instead in response message I receive notification message with separate update message for each leaf node in that subtree. My question is, if I am missing something from official gNMI specification, or I had to setup gnxi target in some special way in order to receive whole subtree as JSON encoded value of one update message.
The text was updated successfully, but these errors were encountered: