You may get a different result due to the upgrading of Spark 3.0: Fail to parse ‘2012-8-7 13:41:28‘

最新推荐文章于 2024-07-10 12:58:03 发布

King of youth

最新推荐文章于 2024-07-10 12:58:03 发布

阅读量2.6k

点赞数 5

分类专栏： spark学习文章标签： spark 大数据 sql 数据库

本文链接：https://blog.csdn.net/fangyu_/article/details/118369790

版权

spark学习专栏收录该内容

2 篇文章 0 订阅

订阅专栏

You may get a different result due to the upgrading of Spark 3.0: Fail to parse '2012-8-7 13:41:28' in the new parser. You can set spark.sql.legacy.timeParserPolicy to LEGACY to restore the behavior before Spark 3.0, or set to CORRECTED and treat it as an invalid datetime string.

加如下配置即可

)

加如下配置即可

	// 加入.config("spark.sql.legacy.timeParserPolicy", "LEGACY")配置一下就不报错了
    val spark: SparkSession = SparkSession
      .builder()
      .appName("Spark SQL")
      .master("local")
      .config("spark.sql.legacy.timeParserPolicy", "LEGACY")
      .getOrCreate()

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

King of youth

关注关注

5
点赞
踩
4

收藏

觉得还不错? 一键收藏
0
评论
You may get a different result due to the upgrading of Spark 3.0: Fail to parse ‘2012-8-7 13:41:28‘

You may get a different result due to the upgrading of Spark 3.0: Fail to parse '2012-8-7 13:41:28' in the new parser. You can set spark.sql.legacy.timeParserPolicy to LEGACY to restore the behavior before Spark 3.0, or set to CORRECTED and treat it as an
复制链接

扫一扫