feat: add tag key prefix queries for namespace-scoped discovery#71
Merged
Conversation
Support querying, counting, and cancelling tasks by tag key prefix (e.g. "billing.") across all layers: TaskStore, Scheduler, ModuleHandle, and DomainHandle. LIKE wildcards in user-supplied prefixes are escaped.
Contributor
Benchmark ComparisonClick to expand |
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
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
tag_keys_by_prefix,tasks_by_tag_key_prefix,count_by_tag_key_prefix,cancel_by_tag_key_prefix) acrossTaskStore,Scheduler,ModuleHandle, andDomainHandlefor discovering and operating on tasks by tag key prefix (e.g."billing.")escape_like_prefix()helper that escapes SQL LIKE wildcards (%,_,\) in user-supplied input before appending the trailing%, ensuring only true prefix matching_with_prefixstore variants that additionally filter bytask_type LIKE 'domain%', consistent with the existing tag query patterndocs/query-apis.md, anddocs/multi-module-apps.mdMotivation
When multiple independent libraries share a single scheduler, each naturally namespaces its tags with a prefix (
billing.customer_id,media.pipeline, etc.). The existing exact-match tag API cannot answer namespace-scoped questions like "how many billing tasks are active?" without knowing every possiblebilling.*key upfront. The new prefix queries fill this gap.Closes #41