Skip to content

[ZEPPELIN-6583] Use selected field for scatter point sizes - #5601

Merged
voidmatcha merged 1 commit into
apache:masterfrom
miinhho:ZEPPELIN-6583-scatter-size
Nov 2, 2026
Merged

voidmatcha merged 1 commit into
apache:masterfrom
miinhho:ZEPPELIN-6583-scatter-size

Conversation

@miinhho

@miinhho miinhho commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

What is this PR for?

The Angular UI saves the selected scatter-chart Size column, but the renderer binds point sizes to the normalized Y values instead. Selecting a different Size column therefore does not change the size mapping.

This PR binds point sizes to the selected column and restores the default point size when the selection is cleared. It preserves the existing Y-value tooltips and group legend rather than allowing G2 to replace tooltip values or add a Size legend.

What type of PR is it?

Bug Fix

What is the Jira issue?

How should this be tested?

Run the focused regression tests from zeppelin-web-angular:

npm run test:shell -- src/app/visualizations/scatter-chart/scatter-chart-visualization.component.spec.ts

For manual verification in the Angular UI, use a paragraph that emits the following tab-separated table output:

%table x   y   size   alternate   group
1   10   2   20   A
2   10   8   8   B
3   10   20   2   A
  1. Select the scatter chart and assign X Axis to x, Y Axis to y, and Group to group.
  2. Assign Size to size. Point sizes should increase from x=1 to x=3 even though all Y values are equal.
  3. Change Size to alternate. The size ordering should reverse while point positions and group colors remain unchanged.
  4. Hover over the points and inspect the legend. Tooltips should still display the Y value (10), and the legend should retain groups A/B without an additional Size legend.
  5. Clear Size. All points should return to the default uniform size.

Questions:

  • Does the license files need to update? No
  • Is there breaking changes for older versions? No
  • Does this needs documentation? No

@voidmatcha voidmatcha left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

As a follow-up, it would be worth considering scaling point areas, as Classic UI does. This could reduce the visual exaggeration of size differences caused by radius-based scaling and keep the behavior consistent with the existing UI.

@voidmatcha
voidmatcha merged commit 3f3463b into apache:master Nov 2, 2026
32 of 36 checks passed
@voidmatcha

Copy link
Copy Markdown
Member

Merged into master (3f3463b).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants