Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Later
-
None
-
None
-
None
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