Gabriel39 opened a new pull request, #69644:
URL: https://github.com/apache/doris/pull/69644

   ### What problem does this PR solve?
   
   Backport #69614 to branch-4.2.
   
   ES HTTP queries do not use FileScannerV2 when `enable_file_scanner_v2` is 
enabled. Add the ES TableReader/FileReader, file-local projection and residual 
filtering, and scroll cleanup from the master implementation.
   
   Branch 4.2 still plans ES through `EsScanNode` and a dedicated ES scanner. 
Adapt that planner to emit FILE_SCAN plans and per-shard ES parameters when v2 
is enabled; disabling the option retains the existing ES plan and scanner. 
Preserve the query DSL, authentication, SSL, docvalue settings, and backend 
assignments. Capture the scanner choice during planning so range assignment 
uses the same protocol without relying on a thread-local context. Reuse 
master's optional Thrift field IDs for the shared and per-shard ES parameters.
   
   Retain branch-4.2's existing Lance v2 dispatch and physical split scheduling.
   
   ### Release note
   
   Support Elasticsearch HTTP queries through FileScannerV2 when 
`enable_file_scanner_v2` is enabled.
   
   ### Check List (For Author)
   
   - Test: 18 FE unit tests, 72 ASAN BE unit tests, clang-format 16, FE 
Checkstyle, and clang-tidy on changed C++ lines.
   - Added ES 5/6/7/8 v1/v2 differential regression coverage; Groovy syntax 
verified. Live external ES regression was not run locally.
   - clang-tidy checks changed C++ lines using a comment-only VFS overlay for 
an existing unmatched NOLINTEND in an unchanged header.
   - Behavior changed: Yes, ES queries honor the scanner session option.
   - Does this need documentation: No, uses the existing scanner option and ES 
catalog properties.
   


-- 
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