Skip to content

WIP: Hive Connector with Amazon S3 documentation updates #18982

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dnanuti wants to merge 1 commit into from
Closed

WIP: Hive Connector with Amazon S3 documentation updates #18982

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion presto-docs/src/main/sphinx/connector/hive.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -487,7 +487,13 @@ Enabling S3 Select Pushdown
You can enable S3 Select Pushdown using the ``s3_select_pushdown_enabled``
Hive session property or using the ``hive.s3select-pushdown.enabled``
configuration property. The session property will override the config
property, allowing you enable or disable on a per-query basis.
property, allowing you enable or disable on a per-query basis. Non-filtering
queries (``SELECT * FROM table``) are not pushed down to S3 Select,
as they retrieve the entire object content.

For uncompressed files, S3 Select scans ranges of bytes in parallel.
The scan range requests run across the byte ranges of the internal
Hive splits for the query fragments pushed down to S3 Select.

Understanding and Tuning the Maximum Connections
################################################
Expand Down