[enhancement](sequence col) add session variable to skip sequence column check while INSERT INTO #41655
+70
−4
Conversation
This file contains hidden or 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
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
zhannngchen
force-pushed
the
fix-insert-into-select-with-seq-col
branch
from
551d6b5 to
85fe1c6
Compare
| "For unique key tables using a sequence column, the INSERT INTO operation requires a sequence value" | ||
| + " to be provided for each row. When this variable is enabled, the check will be skipped" | ||
| }) | ||
| public boolean skipInsertSequenceCheck = false; |
Contributor
There was a problem hiding this comment.
better to use enableInsertSequenceCheck instead
gavinchou
previously approved these changes
Oct 10, 2024
github-actions
bot
added
the
approved
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
Contributor
Author
|
run buildall |
github-actions
bot
removed
the
approved
Contributor
Author
|
run buildall |
Contributor
|
PR approved by at least one committer and no changes requested. |
github-actions
bot
added
the
approved
Yukang-Lian
approved these changes
Oct 11, 2024
zhannngchen
added a commit
to zhannngchen/incubator-doris
that referenced
this pull request
Oct 11, 2024
…umn check while INSERT INTO (apache#41655) For unique key tables using a sequence column, the `INSERT INTO` operation requires a sequence value to be provided for each row. This PR add a new session variable `require_sequence_in_insert` to control this behavior.
zhannngchen
added a commit
to zhannngchen/incubator-doris
that referenced
this pull request
Oct 11, 2024
…umn check while INSERT INTO (apache#41655) For unique key tables using a sequence column, the `INSERT INTO` operation requires a sequence value to be provided for each row. This PR add a new session variable `require_sequence_in_insert` to control this behavior.
zhannngchen
added
dev/2.0.16-merged
dev/2.1.7-merged
and removed
dev/2.0.x
dev/2.1.x
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Proposed changes
Issue Number: close #xxx
For unique key tables using a sequence column, the
INSERT INTOoperation requires a sequence value to be provided for each row.This PR add a new session variable
require_sequence_in_insertto control this behavior.