fix: Apply format fixes missed in previous PRs.

[anlowee]

Description

In #43 we missed a place that was not applied the format fix. This PR makes the change so it is consistent with OSS main repo https://github.com/prestodb/presto/blob/master/presto-native-execution/presto_cpp/main/CMakeLists.txt#L128C1-L132C21.

Checklist

• The PR satisfies the contribution guidelines.
• This is a breaking change and that has been indicated in the PR title, OR this isn't a
  breaking change.
• Necessary docs have been updated, OR no docs need to be updated.

Validation performed

1. Run make format-fix in presto-native-execution.
2. Passed the CI.

Summary by CodeRabbit

• Documentation
  • Updated and condensed comments for improved clarity in build configuration files. No changes to functionality.

[coderabbitai]

Walkthrough

The change updates the comment block above the target_link_libraries command in the CMakeLists.txt file, condensing and rephrasing the notes about dependencies and a TODO. No functional or code-level changes are introduced.

Changes

Cohort / File(s)	Change Summary
CMake Comment Update presto-native-execution/presto_cpp/main/CMakeLists.txt	Condensed and rephrased the comment above the target_link_libraries command; no code changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix: Update native protocol code updates and apply format fixes missed in previous PRs. #43: The main PR and the retrieved PR both modify the comment block above the target_link_libraries(presto_server presto_server_lib velox_tpch_connector) line in the same CMakeLists.txt file, focusing on reformatting and condensing the comment without changing functionality.

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 89ce0f3 and 9e3c06c.

📒 Files selected for processing (1)

• presto-native-execution/presto_cpp/main/CMakeLists.txt (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: anlowee
PR: y-scope/presto#7
File: .github/workflows/hive-tests.yml:33-35
Timestamp: 2025-06-04T14:50:43.554Z
Learning: In the y-scope/presto repository, GitHub workflows are extended from OSS Presto and should maintain consistent formatting with the upstream patterns, including YAML indentation styles for workflow steps.

Learnt from: anlowee
PR: y-scope/presto#0
File: :0-0
Timestamp: 2025-06-19T08:41:46.288Z
Learning: In the y-scope/presto repository, prefer static imports for commonly used methods like String.format(). Instead of writing `String.format("%s", value)`, use static import `import static java.lang.String.format;` and call `format("%s", value)` directly.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (20)

• GitHub Check: test (8.0.442, :presto-tests -P ci-only-plan-determinism)
• GitHub Check: test (17.0.13, :presto-tests -P ci-only-distributed-non-hash-gen)
• GitHub Check: test (17.0.13, :presto-main-base)
• GitHub Check: test (17.0.13, :presto-main)
• GitHub Check: test (17.0.13, :presto-tests -P ci-only-distributed-queries)
• GitHub Check: test (8.0.442, :presto-tests -P ci-only-distributed-queries)
• GitHub Check: test (17.0.13, :presto-tests -P presto-tests-execution-memory)
• GitHub Check: test (8.0.442, :presto-main)
• GitHub Check: test (8.0.442, :presto-tests -P ci-only-resource-manager)
• GitHub Check: test (17.0.13, :presto-tests -P ci-only-local-queries)
• GitHub Check: test (8.0.442, :presto-tests -P ci-only-distributed-non-hash-gen)
• GitHub Check: test (8.0.442, :presto-main-base)
• GitHub Check: test (8.0.442, :presto-tests -P ci-only-tpch-distributed-queries)
• GitHub Check: test (17.0.13, :presto-tests -P presto-tests-general)
• GitHub Check: test (8.0.442, :presto-tests -P presto-tests-general)
• GitHub Check: test (8.0.442, :presto-tests -P presto-tests-execution-memory)
• GitHub Check: maven-checks (17.0.13)
• GitHub Check: maven-checks (8.0.442)
• GitHub Check: prestocpp-linux-build-for-test
• GitHub Check: prestissimo-worker-images-build

🔇 Additional comments (1)

presto-native-execution/presto_cpp/main/CMakeLists.txt (1)

116-117: Formatting aligns with upstream; looks good.
The condensed comment keeps the intent clear while matching OSS Presto style. No further action needed.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.