Uh oh!
There was an error while loading. Please reload this page.
[BugFix](PreparedStatement) fix stmtId overflow - #47950
Merged
Merged
Conversation
if stmtId larger than Interger.MAX_VALUE, there is chance to return `Not supported such prepared statement` to the client which indicates the stmtId not exist.In order to fix this bug: 1. change id from original `stmtId` to `preparedStmtId` in ConnectContext 2. rolling the id to fit the range [0, 2147483647)
eldenmoon
commented
Feb 16, 2025
MemberAuthor
run buildall |
Thearas
commented
Feb 16, 2025
Contributor
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
doris-robot
commented
Feb 16, 2025
TPC-H: Total hot run time: 31594 ms |
doris-robot
commented
Feb 16, 2025
TPC-DS: Total hot run time: 189904 ms |
doris-robot
commented
Feb 16, 2025
ClickBench: Total hot run time: 30.4 s |
eldenmoon
commented
Feb 17, 2025
MemberAuthor
run buildall |
Contributor
PR approved by at least one committer and no changes requested. |
Contributor
PR approved by anyone and no changes requested. |
doris-robot
commented
Feb 17, 2025
TPC-H: Total hot run time: 31770 ms |
doris-robot
commented
Feb 17, 2025
TPC-DS: Total hot run time: 182901 ms |
doris-robot
commented
Feb 17, 2025
ClickBench: Total hot run time: 30.28 s |
morrySnow
approved these changes
Feb 20, 2025
github-actionsBot
pushed a commit
that referenced
this pull request
Feb 20, 2025
if stmtId larger than Interger.MAX_VALUE, there is chance to return `Not supported such prepared statement` to the client which indicates the stmtId not exist.In order to fix this bug: 1. change id from original `stmtId` to `preparedStmtId` in ConnectContext, id which increment in session level and only increment when comming new prepared statement 2. rolling the id to fit the range [-2147483648, 2147483647)
lzyy2024 pushed a commit
to lzyy2024/doris
that referenced
this pull request
Feb 21, 2025
if stmtId larger than Interger.MAX_VALUE, there is chance to return `Not supported such prepared statement` to the client which indicates the stmtId not exist.In order to fix this bug: 1. change id from original `stmtId` to `preparedStmtId` in ConnectContext, id which increment in session level and only increment when comming new prepared statement 2. rolling the id to fit the range [-2147483648, 2147483647)
dataroaring pushed a commit
that referenced
this pull request
Feb 22, 2025
eldenmoon added a commit
to eldenmoon/incubator-doris
that referenced
this pull request
Feb 25, 2025
if stmtId larger than Interger.MAX_VALUE, there is chance to return `Not supported such prepared statement` to the client which indicates the stmtId not exist.In order to fix this bug: 1. change id from original `stmtId` to `preparedStmtId` in ConnectContext, id which increment in session level and only increment when comming new prepared statement 2. rolling the id to fit the range [-2147483648, 2147483647)
yiguolei pushed a commit
that referenced
this pull request
Feb 25, 2025
hubgeter pushed a commit
to hubgeter/doris
that referenced
this pull request
Mar 12, 2025
Closed
koarz pushed a commit
to koarz/doris
that referenced
this pull request
Jun 4, 2025
if stmtId larger than Interger.MAX_VALUE, there is chance to return `Not supported such prepared statement` to the client which indicates the stmtId not exist.In order to fix this bug: 1. change id from original `stmtId` to `preparedStmtId` in ConnectContext, id which increment in session level and only increment when comming new prepared statement 2. rolling the id to fit the range [-2147483648, 2147483647)
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
Sign up for freeto 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.
if stmtId larger than Interger.MAX_VALUE, there is chance to return
Not supported such prepared statementto the client which indicates the stmtId not exist.In order to fix this bug:stmtIdtopreparedStmtIdin ConnectContext, id which increment in session level and only increment when comming new prepared statementWhat problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)