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

   ### What problem does this PR solve?
   
   Related PR: #68687
   
   Pin lance-c to merged upstream main commit 
`cd63420bfbe27f6f0a1edcc873b9191af7d52852`, including the distance-bounded 
search (#90), independent batch nearest search (#92), and boolean 
scalar-segment predicates (#93) changes. Update the archive checksum and 
refresh the existing Foyer patch against that base with an unchanged 
implementation payload.
   
   Foyer PR 
[lance-format/lance-c#73](https://github.com/lance-format/lance-c/pull/73) is 
still open. Its patch must remain temporarily because Doris already calls its 
cache APIs; it can be removed after upstream merge.
   
   This PR changes only `thirdparty/vars.sh` and 
`thirdparty/patches/lance-c-foyer.patch`. The FE predicate converter/planner 
changes, fixtures, and SQL tests in #68687 are not included.
   
   ### Validation
   
   - Verified the downloaded archive checksum and exact patch application.
   - Third-party extraction, cached-source reuse/refresh, and invalid-patch 
rejection tests passed on master.
   - The updated dependency plus the unchanged Foyer patch passed 75 Rust unit 
tests, 376 C API tests, and all 3 native C/C++/static OSS consumer tests.
   - The same dependency passed 27 FE-generated Substrait integration scenarios 
as part of #68687 validation.
   - Full Doris compilation and BE UT for this revision are pending CI.
   
   ### Release note
   
   Update the Lance C dependency to merged upstream search and scalar-predicate 
improvements.
   
   ### Check List (For Author)
   
   - Test: Dependency unit and integration tests described above.
   - Behavior changed: Yes; incorporates upstream lance-c fixes and additive 
APIs.
   - Does this need documentation: No new Doris user interface in this 
dependency-only update.
   


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