Skip to content

Conversation

@dnanuti
Copy link

@dnanuti dnanuti commented Dec 7, 2022

S3 Select pushdown improves queries performance by reducing the data on the wire and it is the most effective when the query pushed down to Select is filtering out a significant portion of the data. This commit disables Select pushdown when the query does not have a predicate or projection. In these cases using GET is both cheaper and faster.

Test plan - (Please fill in how you tested your changes)
Unit tests

Please make sure your submission complies with our Development, Formatting, and Commit Message guidelines. Don't forget to follow our attribution guidelines for any code copied from other projects.

Fill in the release notes towards the bottom of the PR description.
See Release Notes Guidelines for details.

== RELEASE NOTES ==
Hive Changes
* Disable S3 Select pushdown when the query does not have a predicate or projection

@dnanuti dnanuti requested a review from a team as a code owner December 7, 2022 12:58
@dnanuti dnanuti requested a review from presto-oss December 7, 2022 12:58
@dnanuti
Copy link
Author

dnanuti commented Dec 7, 2022

@pettyjamesm please have a look when you find the time

@dnanuti dnanuti force-pushed the select-pushdown-optimisation branch 2 times, most recently from 834eecd to cbee0ea Compare December 7, 2022 15:29
@dnanuti dnanuti force-pushed the select-pushdown-optimisation branch from 89a2f8c to f074a9a Compare December 7, 2022 17:14
S3 Select pushdown improves queries performance by reducing the data
processed on the client side and it is effective when the query pushed
down to Select is filtering out a significant portion of the data.
This commit disables Select pushdown when the query does not have
a predicate or projection. In these cases using GET is both cheaper
and faster.
@dnanuti dnanuti force-pushed the select-pushdown-optimisation branch from f074a9a to 86348b2 Compare December 7, 2022 17:23
Copy link
Contributor

@pettyjamesm pettyjamesm left a comment

Choose a reason for hiding this comment

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

LGTM, @rschlussel - anyone else you know of that should take a look before merging?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants