Skip to content

branch-2.1: [feat](hive) add catalog level partition cache property #50724 #50762

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
yiguolei merged 1 commit into from
May 9, 2025
Merged

branch-2.1: [feat](hive) add catalog level partition cache property #50724 #50762

yiguolei merged 1 commit into from
May 9, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented May 9, 2025

Cherry-picked from #50724

@morningman
[feat](hive) add catalog level partition cache property (#50724)
97fe211 
### What problem does this PR solve?

Problem Summary:
Support enable or disable hive partition cache at Catalog level for hive
catalog.

Previously, if user want to disable the hive partition cache, they can
only set the
`max_hive_partition_table_cache_num=0` in fe.conf and restart FE.
And this config will effect all catalogs.

In this PR, I add a new catalog property `partition.cache.ttl-second`.
If set to 0, the hive partition cache will be disabled, so if new
partitioned is added,
Doris will read the new partition immediately.
@github-actions github-actions bot requested a review from yiguolei as a code owner May 9, 2025 09:07
@Thearas
Copy link
Contributor

Thearas commented May 9, 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 closed this May 9, 2025
@dataroaring dataroaring reopened this May 9, 2025
@Thearas
Copy link
Contributor

Thearas commented May 9, 2025

run buildall

@yiguolei yiguolei merged commit 79056d4 into branch-2.1 May 9, 2025
20 checks passed
@github-actions github-actions bot deleted the auto-pick-50724-branch-2.1 branch May 9, 2025 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei yiguolei 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.

5 participants

@Thearas @yiguolei @dataroaring @morningman