Uh oh!
There was an error while loading. Please reload this page.
[fix](es-catalog) Fix query error when ES keyword field contains array data - #61236
Conversation
Thearas
commented
Mar 11, 2026
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
morningman
commented
Mar 11, 2026
run buildall |
doris-robot
commented
Mar 11, 2026
TPC-H: Total hot run time: 27579 ms |
doris-robot
commented
Mar 11, 2026
TPC-DS: Total hot run time: 153525 ms |
doris-robot
commented
Mar 11, 2026
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
…y data When an Elasticsearch field is mapped as keyword/text but the actual data stored is an array (which is valid in ES), Doris was throwing: 'Expected value of type: STRING; but found type: Array' This fix serializes the array to a JSON string representation instead of throwing an error, which is consistent with how other non-string types (Numbers, Objects) are already handled. Fixed two code paths in es_scroll_parser.cpp: 1. fill_columns() - main _source parsing path 2. handle_value() - array element processing path Also added regression test and test data for this scenario.
6fe4a68 to
a20f5bfComparemorningman
commented
Mar 11, 2026
run buildall |
doris-robot
commented
Mar 11, 2026
TPC-H: Total hot run time: 27489 ms |
doris-robot
commented
Mar 11, 2026
TPC-DS: Total hot run time: 152669 ms |
doris-robot
commented
Mar 11, 2026
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
linrrzqqq
left a comment
There was a problem hiding this comment.
Approved by OpenClaw assistant
PR approved by anyone and no changes requested. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
morningman
commented
Mar 13, 2026
run buildall |
doris-robot
commented
Mar 13, 2026
TPC-H: Total hot run time: 27692 ms |
doris-robot
commented
Mar 13, 2026
TPC-DS: Total hot run time: 153039 ms |
morningman
commented
Mar 13, 2026
run buildall |
doris-robot
commented
Mar 13, 2026
TPC-H: Total hot run time: 27745 ms |
doris-robot
commented
Mar 13, 2026
TPC-DS: Total hot run time: 153217 ms |
hello-stephen
commented
Mar 13, 2026
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Mar 13, 2026
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
PR approved by at least one committer and no changes requested. |
Uh oh!
There was an error while loading. Please reload this page.
…y data (#61236) ### What problem does this PR solve? When an Elasticsearch field is mapped as keyword/text but the actual data stored is an array (which is valid in ES), Doris was throwing: 'Expected value of type: STRING; but found type: Array' This fix serializes the array to a JSON string representation instead of throwing an error, which is consistent with how other non-string types (Numbers, Objects) are already handled. Fixed two code paths in es_scroll_parser.cpp: 1. fill_columns() - main _source parsing path 2. handle_value() - array element processing path Also added regression test and test data for this scenario.
What problem does this PR solve?
When an Elasticsearch field is mapped as keyword/text but the actual data stored is an array (which is valid in ES),
Doris was throwing: 'Expected value of type: STRING; but found type: Array'
This fix serializes the array to a JSON string representation instead of throwing an error,
which is consistent with how other non-string types (Numbers, Objects) are already handled.
Fixed two code paths in es_scroll_parser.cpp:
Also added regression test and test data for this scenario.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)