Skip to content

branch-3.1: [fix](maxcompute)fix maxcompute push down predicates null pointer. #57474 #57567

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
morningman merged 1 commit into from
Oct 31, 2025
Merged

branch-3.1: [fix](maxcompute)fix maxcompute push down predicates null pointer. #57474 #57567

morningman merged 1 commit into from
Oct 31, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Oct 31, 2025

Cherry-picked from #57474

@hubgeter
[fix](maxcompute)fix maxcompute push down predicates null pointer. (#…
70d15ae 
…57474)

### What problem does this PR solve?
Problem Summary:
This PR is a continuation of PR #55635. Based on the current
investigation, the conclusion in PR #55635 appears to be incorrect — the
reason why the predicate column cannot be found in the columnMap remains
unclear.
To help with further debugging, this PR adds additional log information.

In addition, during the `refresh table` process, the
MaxComputeExternalTable object remains unchanged, so the objects it
holds also stay the same. When initializing the table schema, the map
maintained by this object may have repeated `put` operations. So, move
this map to `MaxComputeSchemaCacheValue`, which better matches its
lifecycle and avoids repeated updates during table refresh.
@github-actions github-actions bot requested a review from morrySnow as a code owner October 31, 2025 06:37
@Thearas
Copy link
Contributor

Thearas commented Oct 31, 2025

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?

@dataroaring dataroaring reopened this Oct 31, 2025
@Thearas
Copy link
Contributor

Thearas commented Oct 31, 2025

run buildall

@morningman morningman merged commit 219469c into branch-3.1 Oct 31, 2025
23 checks passed
@github-actions github-actions bot deleted the auto-pick-57474-branch-3.1 branch October 31, 2025 11:46
@morrySnow morrySnow mentioned this pull request Nov 13, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@morrySnow morrySnow morrySnow approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@Thearas @morrySnow @morningman @dataroaring @hubgeter