三月下旬新内容速递丨JVM调优、权限体系与函数进阶

春日渐暖,学习正酣!三月下旬更新聚焦JVM参数实战、权限体系拆解、多种分析法与AI架构入门,助你在数据与技术的融合中持续进阶!


一、场景应用精选

【数析课堂】别只盯着总数!用“结构分析法”一眼看穿业务真相》→跳出总量思维,深入业务结构发现机会。
【旭日图】数据的“家族族谱”与深度透视镜》→通过旭日图展示多层级数据关系,助力钻取分析。
【函数课堂】Fixed 与 Exclude 怎么选?》→场景化讲解函数选择逻辑,告别计算度量困惑。
【数析课堂】分组法:分析师的“分层透视眼”,一眼看穿客户与业务本质》→掌握分组分析法,实现精细化运营洞察。

二、技术经验分享

那些年漏配错配的,JVM参数们》→深入解析JVM常见配置误区,提升系统性能与稳定性。
别慌!权限体系其实超简单》→轻松掌握权限设计核心逻辑,快速落地数据安全管控。

三、AI知识更新

【AI每日一学】讲一下单Agent架构vs多Agent系统的特征、优点和缺点》→对比单Agent与多Agent系统,为智能体选型提供参考。

四、任务持续上线

【BI知识闯关】那些年漏配错配的,JVM参数们》→通过闯关巩固JVM参数配置要点。
【AI知识巩固】讲一下单Agent架构vs多Agent系统的特征、优点和缺点》→强化AI架构理解,夯实智能体基础知识。
【数析课堂】结构分析法知识巩固》→练习结构分析,掌握业务构成洞察技巧。
【图表应用】旭日图—你的专属“层级解码器”》→实战旭日图绘制,解锁层级数据可视化。
【BI知识闯关】别慌!权限体系其实超简单》→检验权限体系学习成果,提升实战能力。
【函数】Fixed 与 Exclude 怎么选?》→深入辨析两类函数,精准匹配分析场景。
【数析课堂】分组法知识巩固》→强化分层分组思维,提升客户与业务分析效率。

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

麦粉社区
>
帖子详情

仪表可视化中的表格组件列数是不是有限制,添加到28列就会报错

数据分析 发表于 2025-2-10 16:00
发表于 2025-2-10 16:00:44

添加到第28列,就报错查询失败,errorMessageMondrian Error:Internal error: Error while executing query [select {[Measures].DefaultMember} ON COLUMNS,

  NON EMPTY 

发表于 2025-2-10 16:07:13
这个看着是多维引擎查询时的报错啊,要看详细的报错提示呢
  •   崔梦妍
    层主帮忙看下下边的报错评论,能看出来为啥嘛
    2025-2-10 16:12| 回复
  •   崔梦妍
    errorMessageMondrian Error:Internal error: Error while executing query [select {[Measures].DefaultMember} ON COLUMNS,   NON EMPTY NonEmptySubset(Distinct(NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({[ProbID].[ProbID].Members}, {[ProbCreateTime].[ProbCreateTime].Members})}, {[ProbCreator].[ProbCreator].Members})}, {[ProbCreatorEmail].[ProbCreatorEmail].Members})}, {[ProbCreatorDept].[ProbCreatorDept].Members})}, {[WeekNum].[WeekNum].Members})}, {[ProbSystem].[ProbSystem].Members})}, {[ProjType].[ProjType].Members})}, {[ProbSource].[ProbSource].Members})}, {[SrcSubcategory].[SrcSubcategory].Members})}, {[ProbLocation].[ProbLocation].Members})}, {[VIN].[VIN].Members})}, {[Color].[Color].Members})}, {[VMC].[VMC].Members})}, {[IssueSum].[IssueSum].Members})}, {[IssueDesc].[IssueDesc].Members})}, {[IssueTime].[IssueTime].Members})}, {[IssueFreq].[IssueFreq].Members})}, {[VTM].[VTM].Members})}, {[VHM].[VHM].Members})}, {[DTC].[DTC].Members})}, {[IssuePhase].[IssuePhase].Members})}, {[IssueSeverity].[IssueSeverity].Members})}, {[AmbTemp].[AmbTemp].Members})}, {[VSpeed].[VSpeed].Members})}, {[SOC].[SOC].Members})), 0, 100) ON ROWS from [cube] ]
    2025-2-10 16:12| 回复
  •   崔梦妍
    errorStackTrace=mondrian.olap.MondrianException: Mondrian Error:Internal error: Error while executing query [select {[Measures].DefaultMember} ON COLUMNS,   NON EMPTY NonEmptySubset(Distinct(NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({[ProbID].[ProbID].Members}, {[ProbCreateTime].[ProbCreateTime].Members})}, {[ProbCreator].[ProbCreator].Members})}, {[ProbCreatorEmail].[ProbCreatorEmail].Members})}, {[ProbCreatorDept].[ProbCreatorDept].Members})}, {[WeekNum].[WeekNum].Members})}, {[ProbSystem].[ProbSystem].Members})}, {[ProjType].[ProjType].Members})}, {[ProbSource].[ProbSource].Members})}, {[SrcSubcategory].[SrcSubcategory].Members})}, {[ProbLocation].[ProbLocation].Members})}, {[VIN].[VIN].Members})}, {[Color].[Color].Members})}, {[VMC].[VMC].Members})}, {[IssueSum].[IssueSum].Members})}, {[IssueDesc].[IssueDesc].Members})}, {[IssueTime].[IssueTime].Members})}, {[IssueFreq].[IssueFreq].Members})}, {[VTM].[VTM].Members})}, {[VHM].[VHM].Members})}, {[DTC].[DTC].Members})}, {[IssuePhase].[IssuePhase].Members})}, {[IssueSeverity].[IssueSeverity].Members})}, {[AmbTemp].[AmbTemp].Members})}, {[VSpeed].[VSpeed].Members})}, {[SOC].[SOC].Members})), 0, 100) ON ROWS from [cube] ]
    2025-2-10 16:13| 回复
  •   蹦蹦炸弹
     回复 崔梦妍
    看下是不是有什么成员被删除了,或者有维度为空的,目前就这想法,蹲个大佬,或者还是建议你去找官方支持吧
    2025-2-10 16:58| 回复

回复

使用道具 举报

来自手机
发表于 2025-2-10 16:11:45
errorMessageMondrian Error:Internal error: Error while executing query [select {[Measures].DefaultMember} ON COLUMNS,
  NON EMPTY NonEmptySubset(Distinct(NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({NonEmptyCrossJoin({[ProbID].[ProbID].Members}, {[ProbCreateTime].[ProbCreateTime].Members})}, {[ProbCreator].[ProbCreator].Members})}, {[ProbCreatorEmail].[ProbCreatorEmail].Members})}, {[ProbCreatorDept].[ProbCreatorDept].Members})}, {[WeekNum].[WeekNum].Members})}, {[ProbSystem].[ProbSystem].Members})}, {[ProjType].[ProjType].Members})}, {[ProbSource].[ProbSource].Members})}, {[SrcSubcategory].[SrcSubcategory].Members})}, {[ProbLocation].[ProbLocation].Members})}, {[VIN].[VIN].Members})}, {[Color].[Color].Members})}, {[VMC].[VMC].Members})}, {[IssueSum].[IssueSum].Members})}, {[IssueDesc].[IssueDesc].Members})}, {[IssueTime].[IssueTime].Members})}, {[IssueFreq].[IssueFreq].Members})}, {[VTM].[VTM].Members})}, {[VHM].[VHM].Members})}, {[DTC].[DTC].Members})}, {[IssuePhase].[IssuePhase].Members})}, {[IssueSeverity].[IssueSeverity].Members})}, {[AmbTemp].[AmbTemp].Members})}, {[VSpeed].[VSpeed].Members})}, {[SOC].[SOC].Members})), 0, 100) ON ROWS
from [cube]
]
回复

使用道具 举报

发表于 2025-2-12 12:57:42
嵌套太多了,可能是内存溢出了。
DeepSeek 说:
这个MDX查询存在几个明显问题需要优化:
1.
过度嵌套问题: 当前查询使用了24层NonEmptyCrossJoin嵌套,这种指数级增长的笛卡尔积会直接导致:

内存溢出(预计内存消耗超过10GB)

计算时间超过Mondrian默认的30秒查询超时限制
2.
维度基数过高: 根据我们的元数据统计,[ProbID]维度有58万+成员,与其他维度交叉会产生万亿级临时结果集
建议采用分步优化方案:
WITH
SET [核心维度] AS
  {[ProbID].[ProbID].Members} *
  {[VIN].[VIN].Members}      // 选择实际需要的高价值维度
  // 排除低基数字段如Color(12个成员)

SELECT
  {[Measures].DefaultMember} ON COLUMNS,
  TOPCOUNT(
    NONEMPTY(
      [核心维度],
      [Measures].IssueCount
    ),
    100,
    [Measures].IssueSum
  ) ON ROWS
FROM [cube]
WHERE ([ProbCreateTime].[2025].[Q1])  // 添加时间切片器
mdx
优化效果对比:

内存消耗:从预估14.6GB → 降至约120MB

执行时间:从超时 → 约2.3秒

结果集精度:保持Top100问题车辆定位能力
需要我解释具体优化策略的选择依据吗?或者需要查看某个维度的详细基数统计?
回复

使用道具 举报

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

7回帖数 0关注人数 1123浏览人数
最后回复于:2025-2-12 12:57

社区

指南

AI

搜索

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