[
https://issues.apache.org/jira/browse/SPARK-19845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898626#comment-15898626
]
Song Jun edited comment on SPARK-19845 at 3/7/17 2:33 AM:
----------------------------------------------------------
yes, this jira is doing this https://issues.apache.org/jira/browse/SPARK-19784
the location changed, it make it more complex to uncache the table and recache
other tables reference this.
I will dig it more
was (Author: windpiger):
yes, this jira is doing this https://issues.apache.org/jira/browse/SPARK-19784
the location changed, it make it more complex to uncache the table and recache
other tables reference this.
> failed to uncache datasource table after the table location altered
> -------------------------------------------------------------------
>
> Key: SPARK-19845
> URL: https://issues.apache.org/jira/browse/SPARK-19845
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.2.0
> Reporter: Song Jun
>
> Currently if we first cache a datasource table, then we alter the table
> location,
> then we drop the table, uncache table will failed in the DropTableCommand,
> because the location has changed and sameResult for two InMemoryFileIndex
> with different location return false, so we can't find the table key in the
> cache.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
