Skip to content

Conversation

@windpiger
Copy link
Contributor

@windpiger windpiger commented Mar 1, 2017

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

@windpiger windpiger changed the title [SPARK-19784][SQL]refresh table after alter the location [SPARK-19784][SQL][WIP]refresh table after alter the location Mar 1, 2017
@SparkQA
Copy link

SparkQA commented Mar 1, 2017

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

SparkQA commented Mar 1, 2017

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.

@windpiger windpiger changed the title [SPARK-19784][SQL][WIP]refresh table after alter the location [SPARK-19784][SQL]refresh table after alter the location Mar 2, 2017
@windpiger windpiger changed the title [SPARK-19784][SQL]refresh table after alter the location [SPARK-19784][SQL][WIP]refresh table after alter the location Mar 2, 2017
@SparkQA
Copy link

SparkQA commented Mar 2, 2017

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
Member

ping @windpiger is this still active?

@asfgit asfgit closed this in 5d2750a May 18, 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:

Closes apache#11129
Closes apache#12085
Closes apache#12162
Closes apache#12419
Closes apache#12420
Closes apache#12491
Closes apache#13762
Closes apache#13837
Closes apache#13851
Closes apache#13881
Closes apache#13891
Closes apache#13959
Closes apache#14091
Closes apache#14481
Closes apache#14547
Closes apache#14557
Closes apache#14686
Closes apache#15594
Closes apache#15652
Closes apache#15850
Closes apache#15914
Closes apache#15918
Closes apache#16285
Closes apache#16389
Closes apache#16652
Closes apache#16743
Closes apache#16893
Closes apache#16975
Closes apache#17001
Closes apache#17088
Closes apache#17119
Closes apache#17272
Closes apache#17971

Added:
Closes apache#17778
Closes apache#17303
Closes apache#17872

## How was this patch tested?

N/A

Author: hyukjinkwon <[email protected]>

Closes apache#18017 from HyukjinKwon/close-inactive-prs.
Sign up for free to 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