Skip to content

Tier 1 Better Metadata Validating and Handling#124

Merged
tokebe merged 2 commits intomainfrom
tier1-meta-cache
Feb 11, 2026
Merged

Tier 1 Better Metadata Validating and Handling#124
tokebe merged 2 commits intomainfrom
tier1-meta-cache

Conversation

@shuchenliu
Copy link
Copy Markdown
Contributor

Solving #116, where an older version of metadata would cause the entire retrieval process to fail on KeyError.

Solving #45 tier1 portion, by enabling the use of bypass_cache flag with get_metadata and its underlying methods. This flag is also internally used when the stale metadata is retrieved from cache for operation generation and a remote refetch is deemed necessary.

@sentry
Copy link
Copy Markdown

sentry bot commented Feb 11, 2026

Codecov Report

❌ Patch coverage is 20.00000% with 12 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
...etriever/data_tiers/tier_1/elasticsearch/driver.py 23.07% 10 Missing ⚠️
.../retriever/data_tiers/tier_1/elasticsearch/meta.py 0.00% 2 Missing ⚠️
Files with missing lines Coverage Δ
.../retriever/data_tiers/tier_1/elasticsearch/meta.py 22.92% <0.00%> (ø)
...etriever/data_tiers/tier_1/elasticsearch/driver.py 43.87% <23.07%> (-2.02%) ⬇️
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@tokebe tokebe merged commit d1afcc4 into main Feb 11, 2026
4 of 5 checks passed
@shuchenliu shuchenliu deleted the tier1-meta-cache branch February 11, 2026 19:02
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