Skip to content

Console: Show Dart sqlQueryId in details pane.#19185

Merged
gianm merged 1 commit intoapache:masterfrom
gianm:web-dart-sqlqueryid
Mar 20, 2026
Merged

Console: Show Dart sqlQueryId in details pane.#19185
gianm merged 1 commit intoapache:masterfrom
gianm:web-dart-sqlqueryid

Conversation

@gianm
Copy link
Contributor

@gianm gianm commented Mar 20, 2026

Show both the unique execution ID (dartQueryId) and the sqlQueryId. This is useful when the sqlQueryId is user-provided and meaningful, and is also useful for correlating with SQL query logs.

Show both the unique execution ID (dartQueryId) and the potentially
sqlQueryId. This is useful when the sqlQueryId is user-provided and
meaningful, and is also useful for correlating with SQL query logs.
Copy link
Contributor

@capistrant capistrant left a comment

Choose a reason for hiding this comment

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

non-blocking suggestion that you can take or leave. overall nice addition

{execution.sqlQueryId && (
<>
{' '}
(SQL ID <Tag minimal>{execution.sqlQueryId}</Tag>)
Copy link
Contributor

Choose a reason for hiding this comment

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

nit. I have no strong preference either way, but maybe keeping the "query" context would be good UX?

Suggested change
(SQL ID <Tag minimal>{execution.sqlQueryId}</Tag>)
(SQL QUERY ID <Tag minimal>{execution.sqlQueryId}</Tag>)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was trying to keep the label short, hopefully it's clear enough.

@gianm gianm merged commit d383fac into apache:master Mar 20, 2026
11 checks passed
@gianm gianm deleted the web-dart-sqlqueryid branch March 20, 2026 15:31
@github-actions github-actions bot added this to the 37.0.0 milestone Mar 20, 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.

2 participants