Song Jun created SPARK-19577:
--------------------------------
Summary: insert into a partition datasource table with
InMemoryCatalog after the partition location alter by alter command failed
Key: SPARK-19577
URL: https://issues.apache.org/jira/browse/SPARK-19577
Project: Spark
Issue Type: Bug
Components: SQL
Affects Versions: 2.2.0
Reporter: Song Jun
If we use InMemoryCatalog, then we insert into a partition datasource table,
which partition location has changed by `alter table t partition(a="xx") set
location $newpath`, the insert operation is ok, and the data can be insert into
$newpath, while if we then select partition from the table, it will not return
the value we inserted.
The reason is that the InMemoryFileIndex to inferPartition by the table's
rootPath, it does not track the user specific $newPath which provided by alter
command.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
