feat: Upgrade velox submodule to y-scope/velox@52bb2f

[wraymo]

Description

This PR is to update the Velox submodule to sync the merged PRs y-scope/velox#42 to have the fix of reading IR files from an unauthenticated HTTP path.

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

Summary by CodeRabbit

• Chores
  • Updated a project dependency to the latest version.

[coderabbitai]

Walkthrough

The Velox submodule pointer in the presto-native-execution project has been updated to a newer commit. No functional code changes or modifications to public declarations are present in this update.

Changes

Cohort / File(s)	Change Summary
Submodule Update presto-native-execution/velox	Submodule commit pointer updated from 425b66f6cb39b9e20cf6801af22aa6126562c999 to 52bb2fedafd6b7ceb12bb60ef959d2a290e82f17

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description is partially complete but has significant gaps when compared against the template. The description and motivation sections are adequately addressed, explaining the purpose of the submodule update. However, several critical sections are missing or empty: the Impact section (addressing public API or user-facing changes) is absent, the Test Plan section shows only an empty placeholder with no validation details provided, and the Release Notes section is not filled in. These omissions represent multiple required template sections left incomplete, which limits the information available for code review and release management.	The author should complete the missing sections by adding an Impact section describing any public API or performance implications of the Velox upgrade, filling in the Test Plan section with details on how the changes were validated, and addressing the Release Notes section using the provided guidelines or indicating if no release notes are required. At minimum, the validation performed section should be completed with concrete testing details rather than left empty.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The PR title "feat: Upgrade velox submodule to y-scope/velox@52bb2f" is concise, follows the Conventional Commits specification, and directly corresponds to the changeset. The title clearly communicates the primary change—upgrading the Velox submodule to a specific commit—making it easy for teammates reviewing history to understand the update. The title is specific and not vague, avoiding generic terms like "misc updates" or "stuff."

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d02268d and 77d882d.

📒 Files selected for processing (1)

• presto-native-execution/velox (1 hunks)

🔇 Additional comments (2)

presto-native-execution/velox (2)

1-1: Commit 52bb2f verified as valid and present in upstream y-scope/velox.

The commit 52bb2fedafd6b7ceb12bb60ef959d2a290e82f17 has been confirmed to exist in the y-scope/velox repository and is associated with PR #42, as indicated by the commit message: "fix: Infer input source for IR files to match behaviour with archive search. (#42)". The verification is complete.

---

1-1: Upstream PR #42 shows incomplete validation; document local testing before merge.

The submodule commit is verified as legitimate and correctly links to y-scope/velox PR #42 (IR reading fix). However, the upstream PR itself has an empty "Validation performed" section, and this Presto PR provides no documentation of local validation or testing performed.

Before merging, please:

1. Document all validation and testing performed locally (build verification, integration tests).
2. Confirm no breaking changes or migrations are required for users consuming this update.
3. If applicable, complete any pre-merge checklist items.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}