You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Song Jun (JIRA)" <ji...@apache.org> on 2017/03/07 01:35:32 UTC

[jira] [Created] (SPARK-19845) failed to uncache datasource table after the table location altered

Song Jun created SPARK-19845:
--------------------------------

             Summary: 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org