十一月上旬更新速递丨 数据与 AI 技术深耕、场景应用拓展与开发进阶实战

秋意正浓时,智能征程不止步!十一月上旬欢度14周年,聚焦数据与AI领域的知识深化、场景化应用落地、技术开发进阶,从理论到实战的全链路能力提升!

一、14周年活动

《14周年·探索乐章 | 寻藏宝图,挖掘社区金矿(已更新1-9关卡)开启一场知识寻宝探险之旅,重温与思迈特并肩成长的温暖时光!

《14周年·温情乐章|写下专属祝福,传递温暖情谊为思迈特14周年注入一份温度,也为这份同行之谊添上一抹亮色!

《14周年·荣誉乐章 | 星光致敬,表彰贡献榜样→回馈大家对社区生态的倾心建设,感谢每一位共建者的热忱与坚守!

二、场景应用

《构建“战略-业务-数据”三层指标体系(体系篇)》→“战略-业务-数据”三层指标体系是AIChat听懂的坚实的底层支撑。

三、术经验分享

《【专家分享】用Smartbi快速搞定数据刷新,老板看了都说好!》→掌握了数据刷新“提速”秘籍:告别滞后,让数据“实时在线”!

《【专家分享】数据排序的“权力游戏”:优先级规则决定谁先谁后》→提供了数据排序指南:破解多指令冲突,明确 “谁先生效”!

四、二次开发视频

扩展包开发前端改造了解前端改造的基本方法与实现流程、如何在Smartbi扩展包中修改CSS样式、扩展JS组件。

、任务持续上线

《【场景实战】数据驱动决策全流程实战:dws层数据处理》→深入数据决策,提升数据整合与维度设计能力,挑战成功即可获得麦豆奖励!

《【AIChat入门闯关计划】-随机掉落小测试》→快速检验AIChat知识漏洞,巩固核心概念。接受挑战即可获得麦豆奖励。

为进一步提升认证服务的质量与体验,我们对认证业务进行全面优化升级。更多详情请看Smartbi认证考试优化升级公告

麦粉社区
>
帖子详情

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中没有这个,注意函数的用法跟实际的数据库是不是匹配
回复

使用道具 举报

发表于 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
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

2回帖数 0关注人数 295浏览人数
最后回复于:2025-10-28 09:39
快速回复 返回顶部 返回列表