JingsongLi opened a new pull request, #41:
URL: https://github.com/apache/paimon-vector-index/pull/41

   ## Summary
   
   Add release-oriented coverage across C, C++, Java/JNI, Python wheel 
packaging, storage-format compatibility, and filter-heavy IVF_HNSW_SQ search 
behavior.
   
   ## Changes
   
   - Expand C and C++ smoke tests to roundtrip all supported index types and 
call `optimize_for_search`.
   - Add C FFI callback error propagation checks for failing write, flush, and 
read callbacks.
   - Extend Java native validation with all-index writer/reader roundtrips.
   - Verify v1 golden fixtures still support `optimize_for_search` without 
changing search results.
   - Add a multi-platform Python wheel CI job for Linux, macOS, and Windows 
that builds and installs wheels, then runs a real roundtrip smoke test.
   - Add `ivfhnswsq_filter_bench` for filter-heavy IVF_HNSW_SQ 
optimized/unoptimized comparison and document it in README.
   
   ## Testing
   
   - `cargo fmt --all -- --check`
   - `cargo clippy --all-targets --workspace -- -D warnings`
   - `cargo test --workspace`
   - `cargo build --release -p paimon-vindex-ffi -p paimon-vindex-jni`
   - Direct C smoke compile/run with `cc`
   - Direct C++ smoke compile/run with `c++`
   - `mvn -f java/pom.xml test`
   - Java native validation with the release JNI library
   - `PYTHONPATH=python 
PAIMON_VINDEX_LIB_PATH=$(pwd)/target/release/libpaimon_vindex_ffi.dylib python 
-m pytest python/tests -q`
   - Local macOS Python wheel build/install/roundtrip smoke
   - Small filter benchmark smoke: `FILTER_BENCH_N=2000 FILTER_BENCH_NQ=20 
FILTER_BENCH_D=16 FILTER_BENCH_NLIST=16 FILTER_BENCH_NPROBE=8 FILTER_BENCH_K=5 
FILTER_BENCH_EF_SEARCH=64 FILTER_BENCH_FILTER_STRIDES=1,8 cargo bench -p 
paimon-vindex-core --bench ivfhnswsq_filter_bench -- --nocapture`
   


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