JingsongLi opened a new pull request, #1206:
URL: https://github.com/apache/paimon-rust/pull/1206

   ## Summary
   
   - Add Java-style `route_builders`, `to_route_result`, and `rank` to hybrid 
search, with owned typed route/result handles. Reuse the same Core fusion 
algorithms for complete queries and independently executed routes.
   - Capture one authorized snapshot for all routes, including empty and 
retained views. Returned vector/full-text builders remain configurable; query 
execution checks happen when execution is requested.
   - Expose pure `HybridSearchRanker` and `HybridSearchWeightedResult` for 
external scored results without table access or query validation.
   - Preserve compatible captured read contexts, and return contextless scores 
for external or conflicting views so ranked reads cannot silently use unrelated 
metadata.
   - Add thin typed Python bindings, matching type stubs and examples. Ranking 
releases the GIL. No dependencies are added.
   
   This covers existing PyPaimon phased hybrid operations. It does not extend 
the physical primary-key hybrid API.
   
   ## Verification
   
   - 30 Core hybrid tests passed, including eight new phase/ranking/context 
tests and existing global, scheduled and PK regressions.
   - Four embedded SDK hybrid tests passed, covering typed objects, all 
rankers, validation, configurable route builders and snapshot ownership.
   - 84 real PyPaimon Native integration cases passed (59 Native plans), using 
the actual registered SDK inside a Cargo test executable. No Native extension 
was installed or rebuilt into a Python environment. The temporary 
cross-repository runner is not committed.
   - Companion Python checks: 167 passed; Arrow 16 focused checks: 23 passed.
   - Rust 1.98.0 all-targets Clippy for Core and bindings with warnings denied, 
rustfmt, type-stub parsing and diff checks passed.
   
   Companion Python PR follows; its Native CI continues to build Rust main.
   
   


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

Reply via email to