maropu commented on a change in pull request #30654:
URL: https://github.com/apache/spark/pull/30654#discussion_r537976124
##########
File path: docs/sql-migration-guide.md
##########
@@ -54,6 +54,8 @@ license: |
- In Spark 3.1, creating or altering a view will capture runtime SQL configs
and store them as view properties. These configs will be applied during the
parsing and analysis phases of the view resolution. To restore the behavior
before Spark 3.1, you can set `spark.sql.legacy.useCurrentConfigsForView` to
`true`.
+ - In Spark 3.1, we support CHAR/CHARACTER and VARCHAR types in our type
system framework instead of replacing them with STRING types. By default, they
can only be used in table schema, not functions/operators. To restore the
behavior before Spark 3.1, which treats them as STRING types and ignores a
length parameter, e.g. `CHAR(4)`, you can set
`spark.sql.legacy.charVarcharAsString` to `true`.
Review comment:
Ur, one more nit comment: `By default, they can...` -> `Currently, they
can...`?
----------------------------------------------------------------
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]
