-
Notifications
You must be signed in to change notification settings - Fork 29.3k
[SPARK-57555][FOLLOWUP][SQL] Add TimeType support to MySQLDialect #57198
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
Open
shrirangmhalgi
wants to merge
4
commits into
apache:master
Choose a base branch
from
shrirangmhalgi:SPARK-57555-mysql-time-dialect
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+144
−3
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
65bebc2
[SPARK-57555][SQL] Support TIME data type in MySQL JDBC dialect
shrirangmhalgi 58c4a4b
Address review patterns from postgres PR: precision via scale, nanos …
shrirangmhalgi 5885ef2
Fix MySQL TIME precision: query INFORMATION_SCHEMA for DATETIME_PRECI…
shrirangmhalgi 38cf5f9
Address MaxGekk R1: TIME(6) fallback, defensive precision guard, fix …
shrirangmhalgi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
These assertions are correct —
TimeType(6)with microseconds preserved is what a nanosecond write should round-trip to. But they don't hold against the current code:getJDBCTypeemits bareTIME(= MySQLTIME(0)) forTimeType(9), so the column stores whole seconds and this reads back asTimeType(0)/12:00:00. On a real MySQL server both assertions would fail. This wasn't caught because the suite is@DockerTestand isn't part of standard PR CI (the description only reports the JDBCSuite unit run). Once thegetJDBCTypefix above lands, these assertions become correct as written — just fix the comment premise below.