-
Notifications
You must be signed in to change notification settings - Fork 3.6k
[Fix](load) Restrict the import of VARCHAR(0) data to avoid coredump #40940
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
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
TPC-H: Total hot run time: 41091 ms
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 193561 ms
|
ClickBench: Total hot run time: 33.13 s
|
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
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
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
…pache#40940) The VARCHAR(0) created has an actual length of 0, and BE didn't restrict it, leading to a BE core dump. #[38427](apache#38427) changed VARCHAR(0) to have a length of 65533. This PR restricts data import when the length is 0 to avoid a core dump.
…pache#40940) The VARCHAR(0) created has an actual length of 0, and BE didn't restrict it, leading to a BE core dump. to have a length of 65533. This PR restricts data import when the length is 0 to avoid a core dump.
The VARCHAR(0) created has an actual length of 0, and BE didn't restrict it, leading to a BE core dump. #38427 changed VARCHAR(0) to have a length of 65533. This PR restricts data import when the length is 0 to avoid a core dump.