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

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

一、场景应用精选

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

二、技术经验分享

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

四、社区日志更新

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

六、任务持续上线

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


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

麦粉社区
>
帖子详情

仪表可视化中的表格组件列数是不是有限制,添加到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关注人数 1024浏览人数
最后回复于:2025-2-12 12:57

社区

指南

AI

搜索

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