-
Notifications
You must be signed in to change notification settings - Fork 592
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
fix: protobuf fixed64 was incorrectly parsed as int64 #12126
Conversation
Codecov Report
@@ Coverage Diff @@
## main #12126 +/- ##
==========================================
+ Coverage 69.77% 69.82% +0.04%
==========================================
Files 1406 1406
Lines 235333 235518 +185
==========================================
+ Hits 164203 164445 +242
+ Misses 71130 71073 -57
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 7 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rest LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lock file changes LGTM
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Protobuf's fixed64 was mapped to RisingWave's int64 (bigint) during create source.
However, prost treats fixed64 as uint64 and then we actually turned uint64 into decimals during parsing. As a result, there was a mismatch between the actual array's type (bigint) and the value's type (decimal).
This PR fixes this bug and map fixed64 to decimal instead.
Additionally, this PR rejects the
map
type in Protobuf. Because we don't yet have a correct handling path. Previously, we convert map toLIST<STRUCT<key VARCHAR, value INT32>>
, which is unexpected.related issue: #10479
Checklist
./risedev check
(or alias,./risedev c
)Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.