三月上旬新内容速递丨选图攻略、内存优化与场景深化

春风送暖,学习相伴!三月上旬更新聚焦数据可视化选图、内存管理技巧、频率分析与桑基图应用,助你轻松驾驭数据分析新场景!

一、场景应用精选

【数析课堂】频率分析:用“数数”快速定位业务痛点》→通过频率统计,快速发现高频问题,精准定位业务改进点。
【桑基图】流动的“资金河流”,一眼看透业务流向》→学习桑基图绘制,追踪资金流动路径,洞察业务流转全貌。

二、技术经验分享

不止选类型,更要找对入口:数据分析选图全攻略》→深入讲解图表选择的核心逻辑,助你告别“图表选择困难症”。
内存溢出别慌张:教你如何看懂BI的“胃”,并管住它的“嘴”》→揭秘BI内存机制,掌握优化技巧,让分析更流畅。

四、社区日志更新

2026年「月更日志」社区更新合集 2.1 - 2.28》→汇总二月社区更新动态,记录成长每一步。

六、任务持续上线

【BI知识闯关】不止选类型,更要找对入口:数据分析选图全攻略》→通过闯关巩固选图知识,提升实战应用能力。
【数析课堂】频率分析知识巩固》→配套练习,加深频率分析理解,强化业务洞察。
【图表应用】桑基图追踪资金流向,发现业务奥秘》→动手实践桑基图,探索资金流向中的业务规律。
【BI知识闯关】内存溢出别慌张:教你如何看懂BI的“胃”,并管住它的“嘴”》→挑战内存管理知识,成为BI优化高手。


阳春三月,学习正当时,快来社区参与挑战,一起探索数据新视界!

麦粉社区
>
帖子详情

ETL追加到关系表,回退SQL时,出现删除数据失败

认证考试 发表于 2025-10-27 09:34
发表于 2025-10-27 09:34:47


2025-10-26 18:09:10.242  [927733] INFO launcher.DefaultLauncher.run:68 [tid=0a0f0215cf9854f2] - Task start. (id:d192e8fb0007323b82247a860756717d,name:JDBC_DATATARGER)

2025-10-26 18:09:10.252  [927733] INFO launcher.DefaultLauncher.run:72 [tid=0a0f0215cf9854f2] - Agent:default

2025-10-26 18:09:10.282  [927733] INFO repository.NodeStatusRepository.executeUpdate:158 [tid=0a0f0215cf9854f2] - Report status successful.(state:RUNNING)

2025-10-26 18:09:10.283  [927733] INFO node.GenericNode.start:108 [tid=0a0f0215cf9854f2] - Node start. (id:d192e8fb0007323b82247a860756717d,name:JDBC_DATATARGER)

2025-10-26 18:09:10.283  [927733] INFO datatarget.JdbcDataTargetNode.checkConfig:330 [tid=0a0f0215cf9854f2] - loaded advanced properties: {}

2025-10-26 18:09:10.311  [927733] INFO datasources.InMemoryFileIndex.logInfo:60 [tid=0a0f0215cf9854f2] - It took 2 ms to list leaf files for 1 paths.

2025-10-26 18:09:10.343  [927733] INFO spark.SparkContext.logInfo:60 [tid=0a0f0215cf9854f2] - Starting job: parquet at DatasetEvent.java:247

2025-10-26 18:09:10.370  [927733] INFO scheduler.DAGScheduler.logInfo:60 [tid=0a0f0215cf9854f2] - Job 297869 finished: parquet at DatasetEvent.java:247, took 0.027076 s

2025-10-26 18:09:10.372  [927733] INFO util.EventSerializeUtil.deserialize:106 [tid=0a0f0215cf9854f2] - Deserialization event finished,took 0.088 s

2025-10-26 18:09:10.372  [927733] INFO datatarget.JdbcDataTargetNode.datasetColumnChange:283 [tid=0a0f0215cf9854f2] - Finish rename the Dataset-Column!

2025-10-26 18:09:10.703  [927733] INFO util.JdbcHelper.execute:262 [tid=0a0f0215cf9854f2] - Incorrect datetime value: '20220241' for function str_to_date

java.sql.SQLException: Incorrect datetime value: '20220241' for function str_to_date

at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:130) ~[mysql-connector-j-8.1.0.jar:8.1.0]

at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122) ~[mysql-connector-j-8.1.0.jar:8.1.0]

at com.mysql.cj.jdbc.StatementImpl.executeInternal(StatementImpl.java:763) ~[mysql-connector-j-8.1.0.jar:8.1.0]

at com.mysql.cj.jdbc.StatementImpl.execute(StatementImpl.java:648) ~[mysql-connector-j-8.1.0.jar:8.1.0]

at smartbix.datamining.engine.util.JdbcHelper.execute(JdbcHelper.java:256) [EngineCore-1.0.jar:?]

at smartbix.datamining.engine.datasource.JdbcHandler.executeRollBackMode(JdbcHandler.java:402) [EngineCore-1.0.jar:?]

at smartbix.datamining.engine.execute.node.datasource.handler.MysqlHandler.executor(MysqlHandler.java:37) [EngineCommonNode-1.0.jar:?]

at smartbix.datamining.engine.execute.node.datatarget.JdbcDataTargetNode.execute(JdbcDataTargetNode.java:177) [EngineCommonNode-1.0.jar:?]

at smartbix.datamining.engine.execute.node.GenericNode.start(GenericNode.java:118) [EngineCore-1.0.jar:?]

at smartbix.datamining.engine.agent.execute.executor.DefaultNodeExecutor.execute(DefaultNodeExecutor.java:60) [EngineAgent-1.0.jar:?]

at smartbix.datamining.engine.agent.execute.launcher.DefaultLauncher.run(DefaultLauncher.java:79) [EngineAgent-1.0.jar:?]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_422]

at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_422]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_422]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_422]

at java.lang.Thread.run(Thread.java:750) [?:1.8.0_422]

2025-10-26 18:09:10.722  [927733] ERROR node.GenericNode.handleExecuteError:150 [tid=0a0f0215cf9854f2] - Node execution failed.(id:d192e8fb0007323b82247a860756717d,name:JDBC_DATATARGER)

smartbix.datamining.engine.execute.exception.ExecuteException: 删除数据执行失败,详情请看日志

at smartbix.datamining.engine.datasource.JdbcHandler.executeRollBackMode(JdbcHandler.java:405) ~[EngineCore-1.0.jar:?]

at smartbix.datamining.engine.execute.node.datasource.handler.MysqlHandler.executor(MysqlHandler.java:37) ~[EngineCommonNode-1.0.jar:?]

at smartbix.datamining.engine.execute.node.datatarget.JdbcDataTargetNode.execute(JdbcDataTargetNode.java:177) ~[EngineCommonNode-1.0.jar:?]

at smartbix.datamining.engine.execute.node.GenericNode.start(GenericNode.java:118) [EngineCore-1.0.jar:?]

at smartbix.datamining.engine.agent.execute.executor.DefaultNodeExecutor.execute(DefaultNodeExecutor.java:60) [EngineAgent-1.0.jar:?]

at smartbix.datamining.engine.agent.execute.launcher.DefaultLauncher.run(DefaultLauncher.java:79) [EngineAgent-1.0.jar:?]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_422]

at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_422]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_422]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_422]

at java.lang.Thread.run(Thread.java:750) [?:1.8.0_422]

Caused by: smartbix.datamining.engine.execute.exception.ExecuteException: java.sql.SQLException: Incorrect datetime value: '20220241' for function str_to_date

at smartbix.datamining.engine.util.JdbcHelper.execute(JdbcHelper.java:263) ~[EngineCore-1.0.jar:?]

at smartbix.datamining.engine.datasource.JdbcHandler.executeRollBackMode(JdbcHandler.java:402) ~[EngineCore-1.0.jar:?]

... 10 more

Caused by: java.sql.SQLException: Incorrect datetime value: '20220241' for function str_to_date

at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:130) ~[mysql-connector-j-8.1.0.jar:8.1.0]

at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122) ~[mysql-connector-j-8.1.0.jar:8.1.0]

at com.mysql.cj.jdbc.StatementImpl.executeInternal(StatementImpl.java:763) ~[mysql-connector-j-8.1.0.jar:8.1.0]

at com.mysql.cj.jdbc.StatementImpl.execute(StatementImpl.java:648) ~[mysql-connector-j-8.1.0.jar:8.1.0]

at smartbix.datamining.engine.util.JdbcHelper.execute(JdbcHelper.java:256) ~[EngineCore-1.0.jar:?]

at smartbix.datamining.engine.datasource.JdbcHandler.executeRollBackMode(JdbcHandler.java:402) ~[EngineCore-1.0.jar:?]

... 10 more

2025-10-26 18:09:10.723  [927733] INFO flow.DistributionFlowContext.notifyNodeFail:538 [tid=0a0f0215cf9854f2] - Number of records outputed:0

2025-10-26 18:09:10.754  [927733] INFO repository.NodeStatusRepository.executeUpdate:158 [tid=0a0f0215cf9854f2] - Report status successful.(state:FAIL)

 


日志里面显示有20220241这种不规范的数值,可是我去报表里面筛选发现没有呀


 

发表于 2025-10-27 09:53:29
回退语句不对,直接执行DELETE where条件用回退语句里面的内容 就知道是怎么回事了
还有,看起来像是ods往dwd写之后dwd数据回退,这个数仓是用mysql搭的? str_to_date函数 oracle中没有这个,注意函数的用法跟实际的数据库是不是匹配
  •   bcd
    我也是这个问题,怎么解决的
    2025-12-15 21:17| 回复

回复

使用道具 举报

发表于 2025-10-28 09:39:20
本帖最后由 橘猫今天喝水了吗 于 2025-10-28 09:41 编辑

Incorrect datetime value: '20220241' for function str_to_date  没有20220241这个时间哦,肯定是你订单日期ID有个20220241的

回复

使用道具 举报

高级模式
B Color Image Link Quote Code Smilies
您需要登录后才可以回帖 登录 | 立即注册

3回帖数 0关注人数 880浏览人数
最后回复于:2025-10-28 09:39

社区

指南

AI

搜索

快速回复 返回顶部 返回列表