Skip to content

Backport 63305 branch 4.0#63738

Open
Gabriel39 wants to merge 3 commits into
apache:branch-4.0from
Gabriel39:backport-63305-branch-4.0
Open

Backport 63305 branch 4.0#63738
Gabriel39 wants to merge 3 commits into
apache:branch-4.0from
Gabriel39:backport-63305-branch-4.0

Conversation

@Gabriel39
Copy link
Copy Markdown
Contributor

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

Gabriel39 added 3 commits May 27, 2026 16:23
Issue Number: close #xxx

Related PR: #xxx

Problem Summary: Add a BE unit test for rejecting Parquet DATA_PAGE_V2 chunks that contain non-dictionary data page encodings in encoding_stats.

None

- Test: Unit Test
    - Added BE UT for RowGroupReader::is_dictionary_encoded DATA_PAGE_V2 encoding_stats handling. Attempted ./run-be-ut.sh --run --filter=ParquetThriftReaderTest.is_dictionary_encoded_rejects_plain_data_page_v2, but local environment has JAVA_HOME on JDK 11 and run-be-ut.sh requires JDK 17. Attempted build-support/clang-format.sh, but local environment lacks llvm@16.
- Behavior changed: No
- Does this need documentation: No
@hello-stephen
Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants