AngersZhuuuu commented on a change in pull request #30421:
URL: https://github.com/apache/spark/pull/30421#discussion_r581938759
##########
File path: docs/sql-ref-syntax-dml-insert-overwrite-table.md
##########
@@ -40,8 +40,8 @@ INSERT OVERWRITE [ TABLE ] table_identifier [ partition_spec
[ IF NOT EXISTS ] ]
* **partition_spec**
- An optional parameter that specifies a comma-separated list of key and
value pairs
- for partitions.
+ An optional parameter that specifies a comma separated list of key and
value pairs
Review comment:
Done
##########
File path: docs/sql-ref-syntax-dml-insert-into.md
##########
@@ -40,8 +40,8 @@ INSERT INTO [ TABLE ] table_identifier [ partition_spec ] [ (
column_list ) ]
* **partition_spec**
- An optional parameter that specifies a comma-separated list of key and
value pairs
- for partitions.
+ An optional parameter that specifies a comma separated list of key and
value pairs
Review comment:
Done
##########
File path: docs/sql-migration-guide.md
##########
@@ -63,6 +63,8 @@ license: |
- In Spark 3.2, the output schema of `SHOW TBLPROPERTIES` becomes `key:
string, value: string` whether you specify the table property key or not. In
Spark 3.1 and earlier, the output schema of `SHOW TBLPROPERTIES` is `value:
string` when you specify the table property key. To restore the old schema with
the builtin catalog, you can set `spark.sql.legacy.keepCommandOutputSchema` to
`true`.
+ - In Spark 3.2, we support using corresponding typed literal of partition
column value type as partition column value in SQL, such as if we have a
partition table with partition column of date type, we can use typed date
literal `date '2020-01-01'` as partition spec `PARTITION (dt = date
'2020-01-01')`, it will be treated as partition column value `2020-01-01`. In
Spark 3.1 and earlier, the partition value will be treated as string value
`date '2020-01-01'` and it's a illegal date type string value and will been
converted to `__HIVE_DEFAULT_PARTITION__`.
Review comment:
DOne
----------------------------------------------------------------
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:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
