lxy-9602 opened a new pull request, #544: URL: https://github.com/apache/paimon-cpp/pull/544
<!-- PR titles must follow Conventional Commits: <type>(<optional-scope>): <description> --> ### Purpose <!-- Linking this pull request to the issue --> Repeated lazy bitmap OR operations retain intermediate unions through supplier chains, increasing memory usage and creating deep recursion when querying many index files. - Materialize bitmap-to-bitmap OR eagerly and return a cached union without retaining its operands. - Return the existing result for zero offsets, avoiding bitmap reconstruction. - Optimize run containers after rebuilding a bitmap for a nonzero offset. <!-- What is the purpose of the change --> ### Tests - Verify that bitmap OR propagates supplier errors immediately. - Verify that zero-offset operations reuse the existing result without invoking its supplier. - Cover run optimization across 32-bit boundaries, preserving row IDs, reducing encoded size, repeated optimization, and empty bitmaps. <!-- Describe tests added or updated and what they cover; explain if no test changes are needed. Omit execution commands, results, and reasons tests were not run locally. --> ### API and Format - Add the public `RoaringBitmap64::RunOptimize()` method. - Bitmap-to-bitmap OR now evaluates suppliers and reports errors during `Or()`. <!-- Does this change affect API in include dir or storage format or protocol --> ### Documentation Update API comments to describe eager bitmap OR, cached results, and the new run optimization method. <!-- Does this change introduce a new feature --> ### Generative AI tooling Generated-by: OpenAI Codex (GPT-6) <!-- If generative AI tooling has been used in the process of authoring this patch, please include the phrase: 'Generated-by: ' followed by the name of the tool and its version. If no, write 'No'. Please refer to the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) for details. --> -- 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]
