feat(native): Add exchange client runtime stats

[kewang1024]

== NO RELEASE NOTE ==

[sourcery-ai]

Reviewer's Guide

This PR expands PrestoExchangeSource to collect and expose three new runtime metrics—getData latency, getDataSize latency, and page size—by adding dedicated metric fields, updating processDataResponse to record values, and modifying the metrics() method to include them when available.

File-Level Changes

Change	Details	Files
Introduce new runtime metric fields	Declared getDataMetric_, getDataSizeMetric_, and pageSizeMetric_ in the class Initialized each metric with appropriate time or byte units	presto-native-execution/presto_cpp/main/PrestoExchangeSource.h
Record values for the new metrics in response processing	Add getDataSizeMetric_.addValue using retry duration for size requests Add getDataMetric_.addValue using retry duration for data requests Add pageSizeMetric_.addValue using totalBytes for data pages	presto-native-execution/presto_cpp/main/PrestoExchangeSource.cpp
Expose new metrics in metrics() override	Initialize result map instead of returning a literal Conditionally insert getDataMs, getDataSizeMs, and pageSizeBytes into the map if count>0 Return the extended result map	presto-native-execution/presto_cpp/main/PrestoExchangeSource.h

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• The metric names like "prestoExchangeSource.getDataMs" suggest milliseconds but you're storing nanosecond values (kNanos) — consider renaming them to "getDataNs" or converting the values to ms to avoid confusion.
• You only include the new metrics in the map when count > 0; consider always emitting them (with zero values) so downstream consumers can rely on a consistent metric schema.
• Instead of multiplying durationMs by 1'000'000 to convert to nanoseconds, consider using std::chrono::duration_cast for more precise and robust unit conversion.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The metric names like "prestoExchangeSource.getDataMs" suggest milliseconds but you're storing nanosecond values (kNanos) — consider renaming them to "getDataNs" or converting the values to ms to avoid confusion.
- You only include the new metrics in the map when count > 0; consider always emitting them (with zero values) so downstream consumers can rely on a consistent metric schema.
- Instead of multiplying durationMs by 1'000'000 to convert to nanoseconds, consider using std::chrono::duration_cast for more precise and robust unit conversion.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[arhimondr]

The max will always be 10s (equal to the long pool duration). We need to substract the time request is waiting for long pool to make it meaningful.