You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2019/10/03 11:27:59 UTC

[GitHub] [spark] karuppayya edited a comment on issue #25995: SPARK-29324: Fix overwrite behaviour for saveAsTable

karuppayya edited a comment on issue #25995: SPARK-29324: Fix overwrite behaviour for saveAsTable 
URL: https://github.com/apache/spark/pull/25995#issuecomment-537824060
 
 
   Without the change,  an external table become a managed table, the file format could change as well(Say table was created using Orc file format, after overwrite it will change to parquet which is the default FF)
   Few issues
   1. Any other user who is consuming the table will be querying the data at an older location, instead of the new location(in this case the warehouse location, since it became a managed table).
   2. In case using overwriting a partitioned table with `partitionOverwriteMode` set to `dynamic`, 
   I think the expectation would be to overwrite the data of the only affected partitions with the same file format(Please correct me if I am wrong). In this case, we will end up writing in a completely different location and maybe with different file format.
   
    

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org