JingsongLi opened a new pull request, #127: URL: https://github.com/apache/paimon-vector-index/pull/127
Range callers currently switch between IVF and DiskANN method names, and the general capability query reports false for DiskANN. This makes `range_search` / `range_search_batch` and their filtered variants work across all five index families, with a common capability query. IVF and DiskANN keep their own tuning parameters; options must match the reader's family and are never reinterpreted. Rust accepts either parameter type through a public tagged enum, C++ adds typed overloads, Java adds a shared options interface while retaining the original method descriptors, and Python dispatches by parameter type. C gains an additive tagged-options entry point for one or more queries and an optional Roaring filter. Existing by-value C layouts, dedicated DiskANN entry points, and legacy result schemas remain compatible. `supports_range_search` intentionally now includes DiskANN. Invalid requests and family mismatches still fail for empty bands, malformed filters remain distinct from absent filters, and results preserve ownership and statistics semantics. Ordinary Top-K traversal, caches, statistics, and the persisted index format are unchanged. Validation against current main (`b8736bb`): - Rust workspace: 754 passed, 2 existing ignored; workspace build, formatting and Clippy with warnings denied passed. - Python: 603 passed, including older/partial native ABI capability behavior and legacy result-schema compatibility. - C/C++ strict warning builds with UBSan and Java/JNI tests passed; each binding passed the shared 168-case core oracle. - Independent compatibility probes covered legacy C++ braced parameters/member pointers and Java null overloads/method descriptors. Boundary tests cover tagged options, pointer/count errors, empty filters, family mismatches and Top-K state preservation. - Tool tests (28), ASF source headers, binary legal inventory, and documentation links passed. -- 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]
