Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add query execution metrics to JDBC QueryStats #24571

Merged
merged 1 commit into from
Dec 24, 2024

Conversation

raunaqmorarka
Copy link
Member

@raunaqmorarka raunaqmorarka commented Dec 24, 2024

Description

Adds planningTimeMillis, analysisTimeMillis, finishingTimeMillis, physicalInputBytes, physicalWrittenBytes and internalNetworkInputBytes to allow JDBC clients to get some important metrics about query execution

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

## JDBC
* Add planningTimeMillis, analysisTimeMillis, finishingTimeMillis, physicalInputBytes, physicalWrittenBytes and internalNetworkInputBytes to JDBC QueryStats. ({issue}`24571`)

@cla-bot cla-bot bot added the cla-signed label Dec 24, 2024
@github-actions github-actions bot added the jdbc Relates to Trino JDBC driver label Dec 24, 2024
Adds planningTimeMillis, analysisTimeMillis, finishingTimeMillis,
physicalInputBytes, physicalWrittenBytes and internalNetworkInputBytes
to allow JDBC clients to get some important metrics about query execution
@raunaqmorarka raunaqmorarka merged commit c6c77cf into trinodb:master Dec 24, 2024
94 checks passed
@raunaqmorarka raunaqmorarka deleted the raunaq/jdbc-stats branch December 24, 2024 18:39
@github-actions github-actions bot added this to the 469 milestone Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed jdbc Relates to Trino JDBC driver
Development

Successfully merging this pull request may close these issues.

2 participants