月下旬更新速递丨 实战场景深化、集成能力升级与开发进阶

初冬来临,一波热气腾腾的更新也准时抵达!我们聚焦实战技巧、集成增强与开发进阶,一系列新功能与新教程,助你在数据分析与系统开发的效率上再进一步。

一、实战技巧精讲

雷达图:多维度数据的“透视镜”,3步读懂数据真相》→ 聚焦雷达图核心应用场景,快速掌握多对象、多维度数据的可视化分析方法。

用图表解锁你的生活“数据密码”!》→ 探索图表在日常场景中的应用,让数据解读更直观、更具操作性。

二、直播上线

2025新特性实战解读(上)数据分析效率倍增秘籍》→ 解析2025新特性落地路径,助力实现数据分析效率成倍提升。

三、技术经验分享

【专家分享】数据排序的“权力游戏”:优先级规则决定谁先谁后》→解读高级排序的业务配置逻辑,让关键数据始终处于优先展示位置。

四、二次开发视频

扩展包开发知识点——前端改造》→从需求分析入手到最终实现的全流程讲解,帮助您快速入门上手Smartbi前端改造。

五、任务持续上线

【初级任务】解锁生活“数据密码”,可视化创意实践任务》→发起可视化创意任务,推动数据表达更生动、更具趣味性。

【初级任务】玩转雷达图解数据,200麦豆等你拿!》→推出雷达图实战任务,以激励方式提升多维数据分析技能。

六、全新素材上线

AD域(LDAP/LDAPS)登录验证V2》→扩展域账号登录支持,实现与企业Windows认证体系无缝对接。

数据模型:对接RestfulAPI接口》→打通数据模型与RestfulAPI对接通道,提升系统集成与数据获取效率。

计划任务:定时清空用户属性缓存→引入缓存自动清理机制,确保权限变更实时生效、业务数据及时更新。

用户同步:BI系统自定义用户所属组》→优化用户组同步逻辑,实现自定义组信息自动识别与补全。

审核流程:可以调用自助ETL》→增强审核流程集成能力,支持在用户任务节点直接调用自助ETL过程。

麦粉社区
>
帖子详情

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关注人数 373浏览人数
最后回复于:2025-10-28 09:39
快速回复 返回顶部 返回列表