-
Notifications
You must be signed in to change notification settings - Fork 329
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: schema validation is skipped once we need to fill a column #2548
fix: schema validation is skipped once we need to fill a column #2548
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #2548 +/- ##
===========================================
- Coverage 85.34% 85.02% -0.33%
===========================================
Files 737 737
Lines 117409 117734 +325
===========================================
- Hits 100206 100106 -100
- Misses 17203 17628 +425 |
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.
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.
LGTM
…timeTeam#2548) * test: test different order * test: add tests for missing and invalid columns * fix: do not skip schema validation while missing columns * chore: use field_columns() * test: add tests for different column order
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
This PR fixes an issue that
WriteRequest::check_schema()
doesn't check the schema of remaining columns inrows
if it finds out that a column is absent but has a default value.It uses a flag to store whether rows have such a column instead of returning directly.
It also adds some tests for input rows with different column order than the region.
Checklist
Refer to a related PR or issue link (optional)
fixes #2547