Closing of Vertica session after the copy command is executed. #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
gerricchaplin
referenced
this pull request
in wandera/aws-lambda-vertica-loader
Sep 8, 2020
WND-21573 - remove duplicate s3:// prefix from the path Approved-by: Ondrej Zivotsky <ondrej.zivotsky@wandera.com>
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.
Lambda loader doesn't close connection to Vertica when the copy statement finishes. This causes hanging of Vertica sessions which are left idle. This eventually eats all the available sessions effectively cutting off all the Vertica clients.