Cherry-pick #16001 to 7.x: Reuse connections on sql module#16027
Merged
jsoriano merged 1 commit intoelastic:7.xfrom Feb 4, 2020
Merged
Cherry-pick #16001 to 7.x: Reuse connections on sql module#16027jsoriano merged 1 commit intoelastic:7.xfrom
jsoriano merged 1 commit intoelastic:7.xfrom
Conversation
Keep a connection open with the database instead of opening and closing connections on each fetch. this is consistent with other specific SQL modules we have. (cherry picked from commit 583a89c)
ChrsMark
approved these changes
Feb 3, 2020
Member
Author
|
jenkins, test this again please ( |
Member
Author
|
A different test failed now, merging. |
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Cherry-pick of PR #16001 to 7.x branch. Original message:
What does this PR do?
Reuse connections between fetches on SQL module.
Why is it important?
Keep a connection open with the database instead of opening and closing connections on each fetch. this is consistent with other specific SQL modules we have, and is usually also prefered by users.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksHow to test this PR locally
Same instructions as in #13257, and then check in the database server that an only connection is created, and it is maintained along the lifetime of the module. This can be checked in MySQL with
SHOW PROCESSLIST.