Add task hub and instance ID prefix orchestration query filters
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 76/100
Research direction
Start with OrchestrationQuery and build_query_instances_req(), then trace their sync and async client callers. Compare the existing query fields with the .NET OrchestrationQuery references and add tests for each filter independently and together; done means both fields serialize into InstanceQuery while omitted fields preserve current requests.
Written by the indexing model from the issue text.
Description
Summary
The protobuf InstanceQuery supports taskHubNames and instanceIdPrefix, and the .NET Durable Task client exposes both filters. Python's OrchestrationQuery and request builder currently omit them.
Current behavior
Python orchestration queries support creation-time bounds, runtime status, result limits, and payload inclusion. There is no way to:
- restrict results to one or more task hubs;
- restrict results to instance IDs beginning with a prefix.
The generated protobuf already contains both fields, so no protocol update is required.
Expected parity
Extend OrchestrationQuery with Python-style equivalents of:
task_hub_names: list[str] | Noneinstance_id_prefix: str | None
Serialize these through build_query_instances_req() to InstanceQuery.taskHubNames and InstanceQuery.instanceIdPrefix for both sync and async clients.
.NET references:
Acceptance criteria
- Callers can filter orchestration queries by task hub names.
- Callers can filter orchestration queries by instance ID prefix.
- Both fields are serialized into the existing protobuf request.
- Existing queries remain backward compatible when the fields are omitted.
- Unit tests cover each filter independently and together.
- Dominant language
- Python
- Stars
- 40
- Forks
- 33
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/durabletask-python
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
microsoft/durabletask-python#268 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
microsoft/durabletask-python#266 ·
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
microsoft/durabletask-python#249 ·
-
bug Functions Parity
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/durabletask-python#241 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
microsoft/durabletask-python#234 ·
All issues in microsoft/durabletask-python
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/dodal#2211 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openml/openml-python#1749 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sipyourdrink-ltd/bernstein#6191 ·