-
Notifications
You must be signed in to change notification settings - Fork 734
Fix check bounds for time extended types #28313
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 check bounds for time extended types #28313
Conversation
|
🟢 |
|
⚪
🟢 |
|
⚪
🟢 |
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.
Pull Request Overview
This PR adds a new parameterized unit test WriteDatetimeValues that validates the writing and reading of Date32, Datetime64, and Timestamp64 values using query parameters for both ROW and COLUMN store tables.
- Adds comprehensive test coverage for Date32, Datetime64, and Timestamp64 parameter types
- Tests extreme values including dates far in the past and future, and edge cases
- Validates both write and read operations with parameterized queries
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Pull Request Overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
|
⚪ ⚪ Ya make output | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
Changelog entry
...
Changelog category
Description for reviewers
This PR fixes two unexpected statuses from BulkUpsert with time extended types (example with Timestamp64):
BAD_REQUESTbut expectedSUCCESS.SUCCESSbut expectedBAD_REQUEST....