[fix](new_json_reader)fix core for new_json_reader#45905
[fix](new_json_reader)fix core for new_json_reader#45905eldenmoon merged 4 commits intoapache:masterfrom
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
|
TeamCity be ut coverage result: |
TPC-H: Total hot run time: 32669 ms |
TPC-DS: Total hot run time: 197527 ms |
ClickBench: Total hot run time: 30.77 s |
| } else { | ||
| return Status::InternalError("Not support load to complex column."); | ||
| } | ||
| // we should set nullmap at last to avoid column_nullable nullmap and data column size not same |
There was a problem hiding this comment.
Why it cause problems if it is in the original position?
BTW, use LLM to generate native English comment.
There was a problem hiding this comment.
According to the original method, we set the nullmap in advance, but if an exception occurs during the logical process of processing data_column below and returns, the size of data_column and nullmap in column_nullable will be inconsistent. Then we catch this exception outter, and call _handle_simdjson_error which calls column pop_back , in this wrong ColumnNullable , data_column which is nullptr would cause core
|
PR approved by anyone and no changes requested. |
|
run buildall |
|
TeamCity be ut coverage result: |
TPC-H: Total hot run time: 32298 ms |
TPC-DS: Total hot run time: 197643 ms |
ClickBench: Total hot run time: 31.58 s |
|
PR approved by at least one committer and no changes requested. |
fix coredump with new_json_reader if we read invalid data will core which source from #43469
What problem does this PR solve?
fix coredump with new_json_reader if we read invalid data will core which source from #43469

Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)