IGNITE-22732 Transaction aware SQL #11438
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nizhikov
changed the title
|
|
||
| /** */ | ||
| @RunWith(Parameterized.class) | ||
| public abstract class AbstractTransactionalSqlTest extends GridCommonAbstractTest { |
There was a problem hiding this comment.
There are no children of this class, only static imports
| @@ -42,7 +42,7 @@ public void testCorrelatesAssignedBeforeAccess() { | |||
| */ | |||
| @Test | |||
| public void testCorrelatesWithTableSpool() { | |||
| sql("CREATE TABLE test(i1 INT, i2 INT)"); | |||
| sql("CREATE TABLE test(i1 INT, i2 INT) WITH atomicity=transactional"); | |||
| @@ -474,6 +446,9 @@ public void testNumericConversion() { | |||
| /** */ | |||
| @Test | |||
| public void testFunctionArgsToNumericImplicitConversion() { | |||
| if (sqlTxMode != SqlTransactionMode.NONE) | |||
There was a problem hiding this comment.
Can we add condition like in executeSql:
if (sqlTxMode != SqlTransactionMode.NONE && tx == null)
startTransaction(ignite);
To assertQuery to avoid such checks in tests?
There was a problem hiding this comment.
assertQuery has check that tx exists in certain modes.
It required to check that test logic correct and starts tx if required.
I skip two tests in DataTypeTest with assumeTrue, because them check only queries without any actual data select.
| .setQueryEntities(F.asList(new QueryEntity(Integer.class, AllTypes.class).setTableName("all_types"))) | ||
| .setBackups(2) | ||
| ); | ||
|
|
|
alex-plekhanov
approved these changes
Sep 19, 2024
nizhikov
added a commit
to nizhikov/ignite
that referenced
this pull request
Oct 7, 2024
nizhikov
added a commit
to nizhikov/ignite
that referenced
this pull request
Oct 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
The description explains WHAT and WHY was made instead of HOW.
The following pattern must be used:
IGNITE-XXXX Change summarywhereXXXX- number of JIRA issue.(see the Maintainers list)
the
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.