flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10817) Upgrade presto dependency to support path-style access
Date Wed, 12 Dec 2018 03:35:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-10817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718425#comment-16718425

ASF GitHub Bot commented on FLINK-10817:

adamlamar commented on issue #7058: [FLINK-10817] Upgrade presto dependency to support path-style
URL: https://github.com/apache/flink/pull/7058#issuecomment-446449939
   @zentol @aljoscha With FLINK-10987 merged, is this ready for another review?

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Upgrade presto dependency to support path-style access
> ------------------------------------------------------
>                 Key: FLINK-10817
>                 URL: https://issues.apache.org/jira/browse/FLINK-10817
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Adam Lamar
>            Assignee: Aljoscha Krettek
>            Priority: Major
>              Labels: pull-request-available
> In order to use any given non-AWS s3 implementation backed by the presto s3 filesystem, it
is necessary to set at least one configuration parameter in flink-conf.yaml:
>  * presto.s3.endpoint: https://example.com
> This appears to work as expected for hosted s3 alternatives.
> In order to use a bring-your-own, self-hosted s3 alternative like [minio|https://www.minio.io/],
at least two configuration parameters are required:
>  * presto.s3.endpoint: https://example.com
>  * presto.s3.path-style-access: true
> However, the second path-style-access parameter doesn't work because the 0.185 version
of presto doesn't support passing through that configuration option to the hive s3 client.
> To work around the issue, path-style-access can be forced on the s3 client by using an
IP address for the endpoint (instead of a hostname). Without this workaround, flink attempts
to use the virtualhost-style at bucketname.example.com, which fails unless the expected DNS
records exist.
> To solve this problem and enable non-IP endpoints, upgrade the [pom|https://github.com/apache/flink/blob/master/flink-filesystems/flink-s3-fs-presto/pom.xml#L36]
to at least 0.186 which includes [this commit|https://github.com/prestodb/presto/commit/0707f2f21a96d2fd30953fb3fa9a9a03f03d88bd]
Note that 0.213 is the latest presto release.

This message was sent by Atlassian JIRA

View raw message