feat(client): Log "Running <query_id>..." in Presto cli in non-interactive mode

[spershin]

Summary:
It is frustrating not to know the query ID, when yopu running a query
from a file or an SQL statement.
This fixes it.

Differential Revision: D96955453

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== NO RELEASE NOTE ==

Summary by Sourcery

Enhancements:

• Add a non-interactive mode message that prints the current query ID before processing status updates.

[linux-foundation-easycla]

• ❌ The email address for the commit (97344e7) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Logs the query ID to the error channel when Presto CLI is running in non-interactive mode so users can see which query is executing.

Sequence diagram for logging query ID in Presto CLI non-interactive mode

sequenceDiagram
    actor User
    participant PrestoCli
    participant Query
    participant StatusPrinter
    participant ErrorChannel
    participant QueryStatusInfo

    User->>PrestoCli: runCliWithSqlOrFile()
    PrestoCli->>Query: renderQueryOutput(out, outputFormat, interactive = false)

    alt non_interactive_mode
        Query->>Query: currentStatusInfo()
        Query->>QueryStatusInfo: getId()
        QueryStatusInfo-->>Query: queryId
        Query->>ErrorChannel: printf(Running %s ..., queryId)
        Query->>StatusPrinter: processInitialStatusUpdates(warningsPrinter)
    else interactive_mode
        Query->>StatusPrinter: printInitialStatusUpdates()
    end

    StatusPrinter-->>PrestoCli: initial status rendered
    PrestoCli-->>User: stdout results, stderr shows Running queryId ...

Loading

File-Level Changes

Change	Details	Files
Log the current query ID when running in non-interactive mode.	In the non-interactive branch of renderQueryOutput, print a message to the error channel indicating the running query ID before processing initial status updates Use client.currentStatusInfo().getId() to obtain and interpolate the query ID in the log message	presto-cli/src/main/java/com/facebook/presto/cli/Query.java

---

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 - I've left some high level feedback:

• Consider guarding the client.currentStatusInfo().getId() call (or reusing an existing status object) to avoid potential null/empty IDs or additional RPCs at this early point in non-interactive execution.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider guarding the `client.currentStatusInfo().getId()` call (or reusing an existing status object) to avoid potential null/empty IDs or additional RPCs at this early point in non-interactive execution.

---

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.}

[skyelves]

LGTM