Description
Right now, with the newly introduced write support of data source API, JSONRelation and ParquetRelation2 both delete data first when the save mode is overwrite (here) and this behavior introduces issues when the destination table is an input table of the query. For example
INSERT OVERWRITE t SELECT * FROM t
We need to add an analysis rule to check cases that are invalid for the write path of data source API.
Attachments
Issue Links
- is related to
-
SPARK-5821 JSONRelation and ParquetRelation2 should check if delete is successful for the overwrite operation.
- Resolved
- links to