morningman opened a new pull request, #61236:
URL: https://github.com/apache/doris/pull/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.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test <!-- At least one of them must be included. -->
       - [ ] Regression test
       - [ ] Unit Test
       - [ ] Manual test (add detailed scripts or steps below)
       - [ ] No need to test or manual test. Explain why:
           - [ ] This is a refactor/code format and no logic has been changed.
           - [ ] Previous test can cover this change.
           - [ ] No code files have been changed.
           - [ ] Other reason <!-- Add your reason?  -->
   
   - Behavior changed:
       - [ ] No.
       - [ ] Yes. <!-- Explain the behavior change -->
   
   - Does this need documentation?
       - [ ] No.
       - [ ] Yes. <!-- Add document PR link here. eg: 
https://github.com/apache/doris-website/pull/1214 -->
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label <!-- Add branch pick label that this PR should 
merge into -->
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to