[SPARK-29525][SQL][TEST] Fix the associated location already exists in SQLQueryTestSuite#26181
Closed
wangyum wants to merge 1 commit into
Closed
[SPARK-29525][SQL][TEST] Fix the associated location already exists in SQLQueryTestSuite#26181wangyum wants to merge 1 commit into
wangyum wants to merge 1 commit into
Conversation
|
Test build #112340 has finished for PR 26181 at commit
|
Member
Author
dongjoon-hyun
approved these changes
Oct 20, 2019
Member
There was a problem hiding this comment.
Thank you for pinging me, @wangyum .
+1, LGTM. Merged to master.
Since the original PostgreSQL test also create temp table and this file is join.sql, this update is more accurate and better.
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
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.
What changes were proposed in this pull request?
This PR fix Fix the associated location already exists in
SQLQueryTestSuite:Why are the changes needed?
Fix bug.
Does this PR introduce any user-facing change?
No
How was this patch tested?
N/A