cloud-fan commented on a change in pull request #32155:
URL: https://github.com/apache/spark/pull/32155#discussion_r612914753
##########
File path: docs/sql-migration-guide.md
##########
@@ -75,6 +75,8 @@ license: |
- In Spark 3.2, `CREATE TABLE .. LIKE ..` command can not use reserved
properties. You need their specific clauses to specify them, for example,
`CREATE TABLE test1 LIKE test LOCATION 'some path'`. You can set
`spark.sql.legacy.notReserveProperties` to `true` to ignore the
`ParseException`, in this case, these properties will be silently removed, for
example: `TBLPROPERTIES('owner'='yao')` will have no effect. In Spark version
3.1 and below, the reserved properties can be used in `CREATE TABLE .. LIKE ..`
command but have no side effects, for example,
`TBLPROPERTIES('location'='/tmp')` does not change the location of the table
but only create a headless property just like `'a'='b'`.
+ - In Spark 3.2, the output schema of `DESCRIBE NAMESPACE` becomes
`info_name: string, info_value: string`. In Spark 3.1 or earlier, the
`info_name` field was named `database_description_item` and the `info_value`
field was named `database_description_value` for the builtin catalog. To
restore the old schema with the builtin catalog, you can set
`spark.sql.legacy.keepCommandOutputSchema` to `true`.
Review comment:
nit: can we put the items for legacy command output schema close to each
other?
--
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]
