Skip to content

Conversation

@J-Bakuli
Copy link
Contributor

@J-Bakuli J-Bakuli commented Dec 6, 2024

IgniteCache#removeAll invocation are not transactional.
But, currently, Ignite allow to invoke clear inside transaction.
This lead to unexpected behavior and hides business logic errors.

We must disallow IgniteCache#removeAll call inside transaction.

TCbot2


Thank you for submitting the pull request to the Apache Ignite.

In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:

The Contribution Checklist

  • There is a single JIRA ticket related to the pull request.
  • The web-link to the pull request is attached to the JIRA ticket.
  • The JIRA ticket has the Patch Available state.
  • The pull request body describes changes that have been made.
    The description explains WHAT and WHY was made instead of HOW.
  • The pull request title is treated as the final commit message.
    The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
  • A reviewer has been mentioned through the JIRA comments
    (see the Maintainers list)
  • The pull request has been checked by the Teamcity Bot and
    the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

If you need any help, please email dev@ignite.apache.org or ask anу advice on http://asf.slack.com #ignite channel.

@J-Bakuli J-Bakuli force-pushed the ignite-23681 branch 2 times, most recently from 3db8a27 to 72c03c7 Compare December 10, 2024 11:55
@timoninmaxim timoninmaxim merged commit 319250b into apache:master Dec 25, 2024
4 of 6 checks passed
@J-Bakuli J-Bakuli deleted the ignite-23681 branch January 24, 2025 07:58
luchnikovbsk pushed a commit to luchnikovbsk/ignite that referenced this pull request Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants