Skip to content

[SPARK-19784][SQL][WIP]refresh table after alter the location - #17119

Closed
windpiger wants to merge 4 commits into
apache:masterfrom
windpiger:alterLocationShouldRefresh
Closed

[SPARK-19784][SQL][WIP]refresh table after alter the location#17119
windpiger wants to merge 4 commits into
apache:masterfrom
windpiger:alterLocationShouldRefresh

Conversation

@windpiger

@windpigerwindpiger commented Mar 1, 2017

Copy link
Copy Markdown
Contributor

What changes were proposed in this pull request?

currently if we alter the location of a table, there are two situations that is not we expected.

  1. we select from it from datasource table, it still return the data of the old location, because cached tableRelation still has the old location.
  2. if the table data is cached before alter the location for both datasource/hive tables, it will return the cached data.

How was this patch tested?

unit test added

@windpigerwindpiger changed the title [SPARK-19784][SQL]refresh table after alter the location[SPARK-19784][SQL][WIP]refresh table after alter the locationMar 1, 2017
@SparkQA

Copy link
Copy Markdown

Test build #73683 has finished for PR 17119 at commit 9050349.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA

Copy link
Copy Markdown

Test build #73690 has finished for PR 17119 at commit dccac9a.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@windpigerwindpiger changed the title [SPARK-19784][SQL][WIP]refresh table after alter the location[SPARK-19784][SQL]refresh table after alter the locationMar 2, 2017
@windpigerwindpiger changed the title [SPARK-19784][SQL]refresh table after alter the location[SPARK-19784][SQL][WIP]refresh table after alter the locationMar 2, 2017
@SparkQA

Copy link
Copy Markdown

Test build #73727 has finished for PR 17119 at commit be98a0f.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@HyukjinKwon

Copy link
Copy Markdown
Member

ping @windpiger is this still active?

@HyukjinKwonHyukjinKwon mentioned this pull request May 17, 2017
zifeif2 pushed a commit to zifeif2/spark that referenced this pull request Nov 22, 2025
## What changes were proposed in this pull request?
This PR proposes to close PRs ...
- inactive to the review comments more than a month
- WIP and inactive more than a month
- with Jenkins build failure but inactive more than a month
- suggested to be closed and no comment against that
- obviously looking inappropriate (e.g., Branch 0.5)
To make sure, I left a comment for each PR about a week ago and I could not have a response back from the author in these PRs below:
Closesapache#11129Closesapache#12085Closesapache#12162Closesapache#12419Closesapache#12420Closesapache#12491Closesapache#13762Closesapache#13837Closesapache#13851Closesapache#13881Closesapache#13891Closesapache#13959Closesapache#14091Closesapache#14481Closesapache#14547Closesapache#14557Closesapache#14686Closesapache#15594Closesapache#15652Closesapache#15850Closesapache#15914Closesapache#15918Closesapache#16285Closesapache#16389Closesapache#16652Closesapache#16743Closesapache#16893Closesapache#16975Closesapache#17001Closesapache#17088Closesapache#17119Closesapache#17272Closesapache#17971
Added:
Closesapache#17778Closesapache#17303Closesapache#17872
## How was this patch tested?
N/A
Author: hyukjinkwon <gurwls223@gmail.com>
Closesapache#18017 from HyukjinKwon/close-inactive-prs.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@windpiger@SparkQA@HyukjinKwon