-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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](jdbc catalog) Use factory methods to return mapped types instead #46623
Merged
Conversation
This file contains 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
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
run buildall |
morningman
previously approved these changes
Jan 8, 2025
github-actions
bot
added
the
approved
Indicates a PR has been approved by one committer.
label
Jan 8, 2025
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
run buildall |
github-actions
bot
removed
the
approved
Indicates a PR has been approved by one committer.
label
Jan 8, 2025
TPC-H: Total hot run time: 32487 ms
|
TPC-DS: Total hot run time: 187338 ms
|
ClickBench: Total hot run time: 31.91 s
|
morningman
approved these changes
Jan 9, 2025
CalvinKirs
approved these changes
Jan 9, 2025
github-actions
bot
added
the
approved
Indicates a PR has been approved by one committer.
label
Jan 9, 2025
PR approved by at least one committer and no changes requested. |
wuwenchi
approved these changes
Jan 9, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Jan 9, 2025
#46623) We should use factory methods to create types instead of returning a type directly, because the returned type is static and final, which will cause problems with length setting.
zy-kkk
added a commit
to zy-kkk/doris
that referenced
this pull request
Jan 9, 2025
apache#46623) We should use factory methods to create types instead of returning a type directly, because the returned type is static and final, which will cause problems with length setting.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
Indicates a PR has been approved by one committer.
dev/2.1.8-merged
dev/3.0.4-merged
reviewed
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.
What problem does this PR solve?
Problem Summary:
We should use factory methods to create types instead of returning a type directly, because the returned type is static and final, which will cause problems with length setting.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)