You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2020/02/26 19:38:00 UTC
[jira] [Commented] (FLINK-15814) Log warning when StreamingFileSink
is used with an ambiguous S3 scheme and error when used with s3p
[ https://issues.apache.org/jira/browse/FLINK-15814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045839#comment-17045839 ]
Steve Loughran commented on FLINK-15814:
----------------------------------------
Out of curiosity, what is the problem?
> Log warning when StreamingFileSink is used with an ambiguous S3 scheme and error when used with s3p
> ---------------------------------------------------------------------------------------------------
>
> Key: FLINK-15814
> URL: https://issues.apache.org/jira/browse/FLINK-15814
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / FileSystem
> Reporter: Seth Wiesman
> Assignee: Seth Wiesman
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> StreamingFileSink does not properly work with bulk output formats and s3-presto. We should log a warning when the provided scheme is 's3p' or 's3' (which is ambiguous) explaining the potential issues and encourage users to only use 's3a' which always delegates to hadoop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)