zjw1111 opened a new issue, #316:
URL: https://github.com/apache/paimon-cpp/issues/316

   ### Search before asking
   
   - [x] I searched in the 
[issues](https://github.com/apache/paimon-cpp/issues) and found nothing similar.
   
   ### Motivation
   
   The bitmap Global Index in Paimon Java has undergone a major redesign. The 
bitmap Global Index currently implemented in Paimon C++ follows the legacy 
design and file format, so it is no longer compatible with the current Java 
implementation.
   
   As a result, Paimon C++ cannot reliably read bitmap Global Index files 
produced by current Paimon Java, and indexes written by the existing C++ 
implementation are not interoperable with the new Java implementation. The 
current Paimon C++ documentation therefore marks bitmap Global Index as 
unsupported.
   
   ### Solution
   
   Reimplement bitmap Global Index in Paimon C++ based on the current Paimon 
Java design and file format. The work should cover:
   
   - The current index reader, writer, and factory behavior.
   - Predicate evaluation and null/non-null bitmap semantics.
   - Compatibility tests using indexes produced by Paimon Java, together with 
C++ round-trip tests.
   - Cleanup or isolation of the legacy implementation after the new 
implementation is validated.
   
   I plan to work on this reimplementation and submit a follow-up PR.
   
   ### Anything else?
   
   The redesigned Java implementation was introduced in 
[apache/paimon#8276](https://github.com/apache/paimon/pull/8276) and 
subsequently integrated with the sorted global-index build path in 
[apache/paimon#8283](https://github.com/apache/paimon/pull/8283).
   
   ### Are you willing to submit a PR?
   
   - [x] I am willing to submit a PR!
   


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