Skip to content

Conversation

@asl3
Copy link
Contributor

@asl3 asl3 commented Jan 12, 2026

What changes were proposed in this pull request?

Display queryId in the Spark SQL UI. This is a follow-up to #53625 which added the UUIDv7 queryId to SQL execution events.

Add queryId column to the All Executions page and Execution detail page. Also add protobuf serialization support for queryId persistence, for History Server.

Why are the changes needed?

The existing executionId is a sequential counter (0, 1, 2...) scoped to a single Spark application; it resets on restart and is not globally unique. queryId is a UUIDv7 that is globally unique and time-ordered, enabling reliable cross-system telemetry and query tracking.

Does this PR introduce any user-facing change?

Yes. The SQL tab now displays a "Query ID" column showing the UUID for each execution.

How was this patch tested?

Manually test the SparkUI view:

Screenshot 2026-01-11 at 8 37 44 PM Screenshot 2026-01-11 at 8 38 01 PM

Updated KVStoreProtobufSerializerSuite to verify queryId round-trips through protobuf serialization.
Existing test fixtures updated for new queryId field

Was this patch authored or co-authored using generative AI tooling?

No

@github-actions
Copy link

JIRA Issue Information

=== Task SPARK-55008 ===
Summary: Display Query ID in Spark UI
Assignee: None
Status: Open
Affected: ["4.2.0"]


This comment was automatically generated by GitHub Actions

@asl3 asl3 changed the title [SPARK-55008] Display Query ID in SparkUI [SPARK-55008][SQL] Display Query ID in SparkUI Jan 12, 2026
Copy link
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

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

+1, LGTM.

@sarutak sarutak changed the title [SPARK-55008][SQL] Display Query ID in SparkUI [SPARK-55008][SQL][WEBUI] Display Query ID in SparkUI Jan 12, 2026
Copy link
Member

@sarutak sarutak left a comment

Choose a reason for hiding this comment

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

LGTM.
@asl3 The CI failure doesn't seem relevant to this change but could you re-trigger GA?

@cloud-fan
Copy link
Contributor

thanks, merging to master!

@cloud-fan cloud-fan closed this in ffb1624 Jan 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants