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

Posted to issues@iceberg.apache.org by GitBox <gi...@apache.org> on 2020/09/08 12:53:14 UTC

[GitHub] [iceberg] skambha commented on issue #1410: Document REPLACE and CREATE OR REPLACE behavior in Spark SQL

skambha commented on issue #1410:
URL: https://github.com/apache/iceberg/issues/1410#issuecomment-688845802


   I can take a look into this.  
   
   I ran a simple test and the current behavior of replace is we are merging the existing properties with the new ones and updating any existing properties with the new values. 
   
   What is the reason we are merging the table properties instead of doing a replace?
   


----------------------------------------------------------------
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



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org