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/11/05 09:13:09 UTC

[GitHub] [spark] dilipbiswal commented on issue #26219: [SPARK-29563][SQL] CREATE TABLE LIKE should look up catalog/table like v2 commands

dilipbiswal commented on issue #26219: [SPARK-29563][SQL] CREATE TABLE LIKE should look up catalog/table like v2 commands
URL: https://github.com/apache/spark/pull/26219#issuecomment-549732697
 
 
   @cloud-fan Thanks !! I did wonder about cross catalog operation as well. I have a question -
   Below is the description of the function ```CreateTableLikeCommand```
   ```
   /**
    * A command to create a table with the same definition of the given existing table.
    * In the target table definition, the table comment is always empty but the column comments
    * are identical to the ones defined in the source table.
    *
    * The CatalogTable attributes copied from the source table are storage(inputFormat, outputFormat,
    * serde, compressed, properties), schema, provider, partitionColumnNames, bucketSpec.
    *
   ```
   So in the case where source is a V1 table and target is a V2 table, we are not able to copy some of the V1 metadata like serde, compressed, inputformat, outputformat etc. Right ? Is that okay ?
   

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