Skip to content
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

enum type is not correctly handeld #214

Open
xemcerk opened this issue Jun 8, 2023 · 1 comment
Open

enum type is not correctly handeld #214

xemcerk opened this issue Jun 8, 2023 · 1 comment

Comments

@xemcerk
Copy link

xemcerk commented Jun 8, 2023

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.

@aisk
Copy link
Member

aisk commented Jun 8, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants