You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We define an enum type in .thrift file, and assign the corresponding field (which is of that enum type) with string, it seems all fine before the request is sent, but we observed that field is missing in log of our server. Is there any way to check how enum filed is transmitted, I presume it's int32, but if so, that wouid be correctly parsed in our server.
The text was updated successfully, but these errors were encountered:
You can using wireshark to capture the request (yes, wireshark have builtin support for thrift). Thus you can know if the field is missed by the client or server.
We define an enum type in .thrift file, and assign the corresponding field (which is of that enum type) with string, it seems all fine before the request is sent, but we observed that field is missing in log of our server. Is there any way to check how enum filed is transmitted, I presume it's int32, but if so, that wouid be correctly parsed in our server.
The text was updated successfully, but these errors were encountered: