[PECOBLR-1146] Feature Flag Cache with Reference Counting #300
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.
Summary
Implement Phase 2 (Per-Host Management - Part 1) of telemetry for the Go driver: feature flag cache with reference counting to prevent rate limiting.
Changes
featureFlagCachestruct with singleton pattern for global cache managementfeatureFlagContextstruct with per-host state (enabled flag, lastFetched, refCount)getOrCreateContext()to increment reference count when connections openreleaseContext()to decrement reference count and cleanup when connections closeisTelemetryEnabled()with 15-minute TTL cache and automatic refreshfetchFeatureFlag()for HTTP integration with Databricks feature flag APIKey Features
sync.RWMutexfor concurrent accessTesting
JIRA
Closes PECOBLR-1146
Part of PECOBLR-1143
Design Document
See
telemetry/DESIGN.mdSection 3.1 for detailed design specification.🤖 Generated with Claude Code
Co-Authored-By: Claude [email protected]