lucasfang opened a new pull request, #523: URL: https://github.com/apache/paimon-cpp/pull/523
### Purpose Backport three main-branch commits to `release-0.4`: - `520acdf79f2e3bef70cd2c9c8512b2119f202822` — correct license attribution and simplify Vortex comments (#518). - `c84520bb50dca0d5a7de6e083962a88f9e3bd7d9` — align guides with the implementation and document local CRoaring modifications (#521). - `b1d588761512956f6d4f7e5028d853a2a657d0a0` — validate byte ranges against known file sizes, skip LM payload range queries when caching is disabled, and use actual file lengths in integration-test splits (#522). The commits retain their original authors and include their source SHAs via `cherry-pick -x`. Resolved one include conflict in the index integration test by retaining both required filesystem headers. Project and documentation versions remain `0.4.0`. ### Tests - `pre-commit run --files` passed for all 21 changed files. - `git diff --check fdad861537a5e70dd372c184ee1f02f375f89c6c HEAD` passed. - Documentation HTML build passed with warnings treated as errors: ```sh PAIMON_DOCS_VERSION=stable sphinx-build -b html -W --keep-going docs/source /tmp/paimon-release04-docs-html ``` The native Debug build is running locally for `paimon-common-test`, `paimon-parquet-format-test`, `paimon-orc-format-test`, `paimon-read-inte-test` and `paimon-write-and-read-inte-with-index-test`. Results will be updated after completion. The PR is opened now to start CI in parallel. ### API and Format No changes to installed public API, storage format or protocol. Invalid byte ranges beyond a known file size now fail before splitting or allocating cache entries. File size zero retains its existing unknown-size meaning. ### Documentation Backports corrected guides, license attribution and CRoaring modification notices. No new feature or configuration option. ### Generative AI tooling Generated-by: OpenAI Codex (codex-cli 0.166.0) -- 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]
