Skip to content

Conversation

@amitkdutta
Copy link
Contributor

== NO RELEASE NOTE ==

@amitkdutta amitkdutta requested review from a team as code owners November 11, 2025 17:40
@prestodb-ci prestodb-ci added the from:Meta PR from Meta label Nov 11, 2025
@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Nov 11, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR advances the Velox submodule to the latest upstream commit and updates associated build, test, and CI configurations to align with API changes.

File-Level Changes

Change Details Files
Bump Velox submodule to new commit
  • Updated submodule pointer to new Velox hash
  • Regenerated build scripts and artifacts
presto-native-execution/velox
Update CI workflows for Velox upgrade
  • Adjusted GitHub Actions to checkout updated submodule
  • Revised Docker image tags for new Velox version
.github/workflows/ci.yml
ci/docker/*
Adapt tests to Velox API changes
  • Modified expected outputs in integration tests
  • Refactored test fixtures to match updated APIs
presto-native-execution/src/test/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

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@czentgr
Copy link
Contributor

czentgr commented Nov 11, 2025

@amitkdutta Lets get a newer Velox version. Deepak's fix for CPR just came in and this helps Prestissimo as well.
Looks like some sidecar issues. Are you aware of anything?

Edit: I'm suspecting the worker is crashing on handling the request. Taking a look.

@czentgr
Copy link
Contributor

czentgr commented Nov 11, 2025

@amitkdutta I found the root cause. A bunch of new iceberg transform functions were added that are internal but get exposed through the API. And they don't conform to the expected function naming convention for (regular) functions.
I can add a commit to ignore them for now. I don't think they are required externally for a user.

name.find("$internal$") != std::string::npos ||
// TODO Review. Iceberg functions, if internal should use the $internal$
// prefix?
name.find("iceberg_") != std::string::npos ||
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@PingLiuPing Newly added Iceberg functions don't conform to the expected name layout. I suspect they are internal for the transformations and are not exposed to the user?
In that case they probably should get the $internal$ prefix? We can clean up Velox later and open an issue if you agree.

Copy link
Contributor Author

@amitkdutta amitkdutta Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@czentgr Thanks for looking. Yea we are experiencing same issue as well. Which PR exposed these functions? Can we revert it? Also we can add something so that the worker does not crash, just skip such functions.

I think its this one: facebookincubator/velox#15440

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@czentgr Thanks.
Those functions should be exposed to users. Currently Presto only support bucket function but Spark(Gluten) support all of them. And those functions has been added to Velox document https://facebookincubator.github.io/velox/functions/iceberg/functions.html.

I will update the code to use three part names.

catalog.schema.function_name

Sorry for the trouble.

@amitkdutta @czentgr

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Newly added Iceberg functions don't conform to the expected name layout

@czentgr Looks like we are lacking documentation for this requirement and PR time testing. Let's follow-up.

Copy link
Contributor

@czentgr czentgr Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@PingLiuPing Yes, Iceberg functions in Velox but are they PrestoSQL functions as well? They can be used through the Velox APIs (PlanBuilder) but are also expected to work in PrestoSQL?

Looks like some iceberg functions are registered using correct prefix: #26581 in PrestoC++.

I think the issue is that Velox is registering the functions itself instead of letting PrestoC++ call the registration (like it does for all the other functions).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@czentgr Suppose those functions been registered by Prestissimo, do we have any mechanisms to get the function prefix inside velox?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if there has been a case where a Velox function was internal but also externalized to PrestoSQL.
We can look. But I would think we have two separate registrations then, once as internal (with the appropriate prefix which gets filtered in prestoc++) and once for PrestoSQL.

amitkdutta added a commit to amitkdutta/velox that referenced this pull request Nov 12, 2025
Summary:
Original commit changeset: ae45744c1ae1

Original Phabricator Diff: D86686271

details: prestodb/presto#26584 (comment)

Reviewed By: abhash09

Differential Revision: D86821554
amitkdutta added a commit to amitkdutta/velox that referenced this pull request Nov 12, 2025
…ms" (facebookincubator#15475)

Summary:

Original commit changeset: ae45744c1ae1

Original Phabricator Diff: D86686271

details: prestodb/presto#26584 (comment)

Reviewed By: abhash09

Differential Revision: D86821554
meta-codesync bot pushed a commit to facebookincubator/velox that referenced this pull request Nov 12, 2025
…ms" (#15475)

Summary:
Pull Request resolved: #15475

Original commit changeset: ae45744c1ae1

Original Phabricator Diff: D86686271

details: prestodb/presto#26584 (comment)

Reviewed By: kgpai, tanjialiang, abhash09

Differential Revision: D86821554

fbshipit-source-id: 79bf0de3deec19ba5d8cd720a3abef05dc29e94b
@czentgr czentgr merged commit 0e12d41 into prestodb:master Nov 12, 2025
112 of 113 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

from:Meta PR from Meta

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants