Allow DBDagBag TTL cache eviction without a size cap#69774
Open
aeroyorch wants to merge 2 commits into
Open
Conversation
aeroyorch
force-pushed
the
dbdagbag-ttl-only-cache
branch
from
dc1b483 to
379aa9e
Compare
aeroyorch
force-pushed
the
dbdagbag-ttl-only-cache
branch
from
379aa9e to
a112469
Compare
aeroyorch
changed the title
DBDagBag TTL cache eviction without a size cap
SameerMesiah97
left a comment
SameerMesiah97
left a comment
Contributor
There was a problem hiding this comment.
Just one nit. Looks good otherwise.
Contributor
Author
Thanks for the review! Changes already implemented |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Allow
DBDagBagTTL cache eviction without a size cap (i.e.cache_size=0,cache_ttl>0).Related to #69001 and #69007
Was generative AI tooling used to co-author this PR?
Claude Opus 4.8 to analyze the impact of this change in terms of docs/code.
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.