-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[Fix](jdbc-scanner) Fix jdbc scanner memory leak because it didn't close outputTable
.
#41041
[Fix](jdbc-scanner) Fix jdbc scanner memory leak because it didn't close outputTable
.
#41041
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
outputTable
.outputTable
.
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. |
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
TPC-H: Total hot run time: 41907 ms
|
TPC-DS: Total hot run time: 194575 ms
|
ClickBench: Total hot run time: 33.06 s
|
run external |
1 similar comment
run external |
…ose `outputTable`. (apache#41041) ## Proposed changes [Fix] (jdbc-scanner) Fix jdbc scanner memory leak because it didn't close `outputTable`.
…ose `outputTable`. (#41041) ## Proposed changes [Fix] (jdbc-scanner) Fix jdbc scanner memory leak because it didn't close `outputTable`.
…ose `outputTable`. (apache#41266) ## Proposed changes Backport apache#41041.
Proposed changes
[Fix] (jdbc-scanner) Fix jdbc scanner memory leak because it didn't close
outputTable
.