-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[BugFix](PreparedStatement) fix stmtId overflow #47950
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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)
|
run buildall |
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
TPC-H: Total hot run time: 31594 ms |
TPC-DS: Total hot run time: 189904 ms |
ClickBench: Total hot run time: 30.4 s |
|
run buildall |
qidaye
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
TPC-H: Total hot run time: 31770 ms |
TPC-DS: Total hot run time: 182901 ms |
ClickBench: Total hot run time: 30.28 s |
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)
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)
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)
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)
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)