Skip to content

Deprecate ChainedTransactionManager #2286

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Deprecate ChainedTransactionManager #2286

wants to merge 2 commits into from

Conversation

mp911de
Copy link
Member

@mp911de mp911de commented Jan 29, 2021

We recommend to not use ChainedTransactionManager as it emulates distributed transactions without providing consistency guarantees that can end up in partially committed transactions. To attach to commit/rollback operations we recommend registering TransactionSynchronization instead.

Closes #2232.

We recommend to not use ChainedTransactionManager as it emulates distributed transactions without providing consistency guarantees that can end up in partially committed transactions. To attach to commit/rollback operations we recommend registering TransactionSynchronization instead.

See #2232.
@mp911de mp911de added the for: team-attention An issue we need to discuss as a team to make progress label Jan 29, 2021
christophstrobl pushed a commit that referenced this pull request Feb 2, 2021
We recommend to not use ChainedTransactionManager as it emulates distributed transactions without providing consistency guarantees that can end up in partially committed transactions. To attach to commit/rollback operations we recommend registering TransactionSynchronization instead.

Closes #2232
Original Pull Request: #2286
@christophstrobl christophstrobl deleted the issue/2232 branch February 2, 2021 13:50
* <p/>
* Instead of using {@link ChainedTransactionManager} for attaching callbacks to transaction commit (pre commit/post
* commit), either register a {@link org.springframework.transaction.reactive.TransactionSynchronization} to explicitly
* follow transaction cleanup with simplified semantics in case of exceptions.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This "either" seems to be missing an "or".

@OrangeDog
Copy link

This didn't make it into the release notes?
https://spring.io/blog/2021/04/20/what-s-new-in-spring-data-2021-0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: team-attention An issue we need to discuss as a team to make progress
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Deprecate ChainedTransactionManager [DATACMNS-1817]
4 participants