temporalio / temporalio/sdk-java
Allow more granular setting of QueryRejectCondition
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
Expected Behavior
We should be able to specify QueryRejectCondition for each query or at least for each specific workflow stub to have a granular enough control.
Actual Behavior
Right now the only way to specify QueryRejectCondition in JavaSDK is on WorkflowClientOptions, which means that once the rejection level is specified, it will be applied for all queries for all workflows queried from the client.
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.
Research direction
Start with QueryRejectCondition and WorkflowClientOptions in the Java SDK, then trace how query requests reach workflow stubs. Determine the API surface needed for per-query or per-workflow-stub configuration, and add tests showing that different queries can use different rejection settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100