Investigate rollbackEntityOperationsOnExceptions semantics for Durable Entities

Open
#241 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
distributed-systems

Research direction

Start with the upstream report and the Python entity request for Durable Entities v2, then compare it with the host rollbackEntityOperationsOnExceptions setting and the gRPC or extension/protobuf contract. Exercise the listed mutation, batching, failure, and retry cases, followed by end-to-end host coverage for supported v2 providers. Done means the semantics are verified, or the required extension/protobuf work is identified and linked instead of adding SDK-only behavior.

Written by the indexing model from the issue text.

Description

bug Functions Parity

Upstream report: https://github.com/Azure/azure-functions-durable-python/issues/274

Investigate whether azure-functions-durable v2 entities honor the host rollbackEntityOperationsOnExceptions setting. This may require a Durable Functions extension or wire-contract change if the setting is not available in the Python entity request.

Investigation goals

  • Verify omitted/default and explicit true: set, delete, create, and in-place mutation followed by an exception are rolled back.
  • Verify explicit false: those mutations remain applied.
  • Verify that, in a multi-operation batch, only the failed operation is rolled back and successful operations before and after it remain applied.
  • Verify callers observe the operation failure without an unintended retry.
  • Add end-to-end host coverage for supported v2 providers.
  • If the gRPC or extension contract cannot carry this option, identify and link the required extension/protobuf work rather than implementing SDK-only behavior.
Dominant language
Python
Stars
40
Forks
33
Avg merge
2d 2h
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/durabletask-python

All issues in microsoft/durabletask-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.