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-8432) Add openstack swift filesystem
Date Mon, 15 Jan 2018 12:11:00 GMT

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

ASF GitHub Bot commented on FLINK-8432:

Github user jelmerk commented on the issue:

    Hi @tillrohrmann Those files with a lot of changes  are unfortunately copied from hadoop,
the readme file contains more information about how this works. I am not overly happy about
the this approach. But its basically the exact same approach that was taken for the s3 connector

> Add openstack swift filesystem
> ------------------------------
>                 Key: FLINK-8432
>                 URL: https://issues.apache.org/jira/browse/FLINK-8432
>             Project: Flink
>          Issue Type: Improvement
>          Components: filesystem-connector
>    Affects Versions: 1.4.0
>            Reporter: Jelmer Kuperus
>            Priority: Major
>              Labels: features
> At ebay classifieds we started running our infrastructure on top of OpenStack.
> The openstack project comes with its own amazon-s3-like filesystem, known as Swift. It's
built for scale and optimized for durability, availability, and concurrency across the entire
data set. Swift is ideal for storing unstructured data that can grow without bound.
> We would really like to be able to use it within flink without Hadoop dependencies, as
a sink or for storing savepoints etc
> I've prepared a pull request that adds support for it. It wraps the hadoop support for
swift in a way that is very similar to the way the s3 connector works.
> You can find out more about the underlying hadoop implementation at [https://hadoop.apache.org/docs/stable/hadoop-openstack/index.html]
> Pull request : [https://github.com/apache/flink/pull/5296]

This message was sent by Atlassian JIRA

View raw message