JeonDaehong commented on PR #1177:
URL: https://github.com/apache/paimon-rust/pull/1177#issuecomment-6315008390
Added a second commit after checking BTree. BTree keys keep `total_cmp`
order, so once the residual follows Java, a table with a BTree index answered
differently from a scan without one. `> 0` and `>= -1` dropped sign-bit NaN
rows, and `= NaN` / `IN (NaN)` matched only one NaN payload. On main the two
agree because both use bit order.
The fix keeps exact BTree answers wherever the key order can't matter. NaN
literals are canonicalized. Only a file whose keys hold NaNs, at its first key
for ranges or at either end for NaN literals, leaves that predicate to the row
filter. Meta pruning and the all-match shortcut skip such files too.
`test_bitmap_floating_candidates_preserve_residual_results` now also runs on
BTree and covers `>` / `>=`. `test_evaluate_legacy_{float,double}_btree` and
`test_bitmap_floating_bound_fusion_preserves_candidates_and_fallback` pinned
bit-order answers for NaN literals and bounds, so they now expect the Java
result.
--
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]
