IgniteCache#clear invocation are not transactional.
But, currently, Ignite allow to invoke clear inside transaction.
This lead to unexpected behaviour and hides business logic errors.
We must disallow IgniteCache#clear call inside transaction.
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)
zstan
commented
1 week ago
IgniteCache#clearinvocation are not transactional. But, currently, Ignite allow to invokeclearinside transaction. This lead to unexpected behaviour and hides business logic errors.We must disallow IgniteCache#clear 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
IGNITE-XXXX Change summarywhereXXXX- number of JIRA issue.green visaattached 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.