Do not create a job status table for external tables #309
Conversation
This file contains 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
...src/main/scala/com/vertica/spark/datasource/core/VerticaDistributedFilesystemWritePipe.scala
Outdated
Show resolved
Hide resolved
...test/scala/com/vertica/spark/datasource/core/VerticaDistributedFilesystemWritePipeTest.scala
Show resolved
Hide resolved
alexey-temnikov
approved these changes
Jan 14, 2022
Sign up for free
to 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.
Summary
Do not create a job status table for external tables.
Description
When using external tables, do not create the status table in Vertica. For non-external tables, the status table is still created.
In the future we will add an option to make the status table optional for non-external tables as well (see #308).
Related Issue
Closes #290
Additional Reviewers
@alexey-temnikov
@alexr-bq
@jonathanl-bq
@Aryex