[
https://issues.apache.org/jira/browse/FLINK-8175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274140#comment-16274140
]
Till Rohrmann commented on FLINK-8175:
--------------------------------------
I agree that we should move {{flink-statebackend-rocksdb}} into its
own/state-backend module or {{flink-runtime}} package.
I think the {{flink-connector-wikiedits}} is mainly used in our example
quickstarts. This allows people to get quickly started. However, I'm not sure
how relevant this still is. I wouldn't object to move it to Bahir.
The same applies a bit to Flink's Storm integration. In terms of maintenance I
would be in favour of moving it to Bahir as well. But I'm not entirely sure how
many people actively use it.
> remove flink-streaming-contrib and migrate its classes to
> flink-streaming-java/scala
> ------------------------------------------------------------------------------------
>
> Key: FLINK-8175
> URL: https://issues.apache.org/jira/browse/FLINK-8175
> Project: Flink
> Issue Type: Improvement
> Affects Versions: 1.5.0
> Reporter: Bowen Li
>
> I propose removing flink-streaming-contrib from flink-contrib, and migrating
> its classes to flink-streaming-java/scala for the following reasons:
> - flink-streaming-contrib is so small that it only has 4 classes (3 java and
> 1 scala), and they don't need a dedicated jar for Flink to distribute and
> maintain it and for users to deal with the overhead of dependency management
> - the 4 classes in flink-streaming-contrib are logically more tied to
> flink-streaming-java/scala, and thus can be easily migrated
> - flink-contrib is already too crowded and noisy. It contains lots of sub
> modules with different purposes which confuse developers and users, and they
> lack a proper project hierarchy
> To take a step even forward, I would argue that even flink-contrib should be
> removed and all its submodules should be migrated to other top-level modules
> for the following reasons: 1) Apache Flink the whole project itself is a
> result of contributions from many developers, there's no reason to highlight
> some contributions in a dedicated module named 'contrib' 2) flink-contrib
> inherently doesn't have a good hierarchy to hold submodules
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
