IGNITE-10516 Fix duplicate index error after CREATE INDEX IF NOT EXISTS on different tables #10940
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
shishkovilja
force-pushed
the
ignite-10516
branch
from
2c78b2e to
23ac39e
Compare
|
SonarCloud Quality Gate failed.
|
shishkovilja
force-pushed
the
ignite-10516
branch
3 times, most recently
from
0c5a48c to
1e5772b
Compare
shishkovilja
force-pushed
the
ignite-10516
branch
from
1e5772b to
62bf795
Compare
shishkovilja
force-pushed
the
ignite-10516
branch
from
829b62f to
e8797a3
Compare
…TS on different tables
shishkovilja
force-pushed
the
ignite-10516
branch
from
eab6a4a to
a086772
Compare
NSAmelchev
approved these changes
Oct 31, 2023
J-Bakuli
pushed a commit
to J-Bakuli/ignite
that referenced
this pull request
Nov 10, 2023
…ISTS on different tables (apache#10940)
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.
Description
PR adds no-op flag to
SchemaFinishDiscoveryMessageandSchemaOperationStatusMessagein order to avoid undesirable storing of cache configuration and query entity patching inGridQueryProcessor#onSchemaFinishDiscoveryThank 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.