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

[#6656 ] fix(trino-connector): support read MySQL time/datetime/timestamp columns with precision #6657

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

predator4ann
Copy link
Contributor

@predator4ann predator4ann commented Mar 10, 2025

Why are the changes needed?

Fix: #6656

Does this PR introduce any user-facing change?

No

How was this patch tested?

UT already added.

Signed-off-by: zacsun <zacsun@lilith.com>
Signed-off-by: zacsun <zacsun@lilith.com>
@jerqi jerqi requested a review from diqiu50 March 10, 2025 11:11
Signed-off-by: zacsun <zacsun@lilith.com>
Signed-off-by: zacsun <zacsun@lilith.com>
@yuqi1129 yuqi1129 requested a review from mchades March 11, 2025 07:33
default:
throw new TrinoException(
GravitinoErrorCode.GRAVITINO_ILLEGAL_ARGUMENT,
"Invalid timestamp precision: " + precision + ". Valid values are 0, 3, 6, 9");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are two problems:

  1. Is mysql support timestamp(9)?
  2. The error message should like "Invalid mysql timestamp precision".

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

Successfully merging this pull request may close these issues.

[Bug report] Trino Connector Fails to Read MySQL Timestamp Columns with Precision
3 participants