gengliangwang commented on a change in pull request #33176:
URL: https://github.com/apache/spark/pull/33176#discussion_r662485470



##########
File path: 
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/parser/AstBuilder.scala
##########
@@ -2502,7 +2502,7 @@ class AstBuilder extends SqlBaseBaseVisitor[AnyRef] with 
SQLConfHelper with Logg
       case ("float" | "real", Nil) => FloatType
       case ("double", Nil) => DoubleType
       case ("date", Nil) => DateType
-      case ("timestamp", Nil) => TimestampType
+      case ("timestamp", Nil) => SQLConf.get.timestampType

Review comment:
       I would prefer doing that in seperate PRs to keep this one clean. We 
should support the new keyword both on data type parsing and the type literals.
   https://issues.apache.org/jira/browse/SPARK-35977
   https://issues.apache.org/jira/browse/SPARK-35978

##########
File path: 
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/parser/AstBuilder.scala
##########
@@ -2502,7 +2502,7 @@ class AstBuilder extends SqlBaseBaseVisitor[AnyRef] with 
SQLConfHelper with Logg
       case ("float" | "real", Nil) => FloatType
       case ("double", Nil) => DoubleType
       case ("date", Nil) => DateType
-      case ("timestamp", Nil) => TimestampType
+      case ("timestamp", Nil) => SQLConf.get.timestampType

Review comment:
       I would prefer doing that in separate PRs to keep this one clean. We 
should support the new keyword both on data type parsing and the type literals.
   https://issues.apache.org/jira/browse/SPARK-35977
   https://issues.apache.org/jira/browse/SPARK-35978




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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to