You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Andrey Zagrebin (JIRA)" <ji...@apache.org> on 2019/06/17 13:40:00 UTC
[jira] [Updated] (FLINK-12873) Create a separate maven module for
Shuffle API
[ https://issues.apache.org/jira/browse/FLINK-12873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Zagrebin updated FLINK-12873:
------------------------------------
Description:
At the moment, shuffle service API is a part of flink-runtime maven module. The implementers of other shuffle services will have to depend on the fat dependency of flink-runtime. We should consider factoring out the shuffle API interfaces into a separate maven module which depends only on flink-core. Later we can consider the same for the custom high availability services.
The final structure could be e.g. (up to discussion):
* flink-runtime (already includes default shuffle and high availability implementations)
* flink-runtime-extensions
** flink-runtime-extensions-core
** flink-shuffle-extensions-api
** flink-high-availability-extensions-api
was:
At the moment, shuffle service API is a part of flink-runtime maven module. The implementers of other shuffle services will have to depend on the fat dependency of flink-runtime. We should consider factoring out the shuffle API interfaces to a separate maven module which depends only on flink-core. Later we can consider the same for the custom high availability services.
The final structure could be e.g. (up to discussion):
* flink-runtime (already includes default shuffle and high availability implementations)
* flink-runtime-extensions
** flink-runtime-extensions-core
** flink-shuffle-extensions-api
** flink-high-availability-extensions-api
> Create a separate maven module for Shuffle API
> ----------------------------------------------
>
> Key: FLINK-12873
> URL: https://issues.apache.org/jira/browse/FLINK-12873
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Configuration, Runtime / Network
> Reporter: Andrey Zagrebin
> Priority: Major
>
> At the moment, shuffle service API is a part of flink-runtime maven module. The implementers of other shuffle services will have to depend on the fat dependency of flink-runtime. We should consider factoring out the shuffle API interfaces into a separate maven module which depends only on flink-core. Later we can consider the same for the custom high availability services.
> The final structure could be e.g. (up to discussion):
> * flink-runtime (already includes default shuffle and high availability implementations)
> * flink-runtime-extensions
> ** flink-runtime-extensions-core
> ** flink-shuffle-extensions-api
> ** flink-high-availability-extensions-api
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)