[
https://issues.apache.org/jira/browse/FLINK-18783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367150#comment-17367150
]
Chesnay Schepler commented on FLINK-18783:
------------------------------------------
The new flink-rpc-akka module (to be added in FLINK-23089) will assemble a fat
jar containing Akka and all of it's transitive dependencies, including scala.
This jar will be bundled in flink-runtime as-is (i.e., there is literally
another jar in the flink-runtime jar). This jar will be extracted on-demand
when the AkkaRpcSystem (FLINK-23090) is required. To load the AkkaRpcSystem we
will then point a PluginLoader to that location.
This has the significant advantage that we'll get the same dependency isolation
that we get at runtime also in tests or when running example in the IDE.
> Load AkkaRpcService through separate class loader
> -------------------------------------------------
>
> Key: FLINK-18783
> URL: https://issues.apache.org/jira/browse/FLINK-18783
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.10.1, 1.11.1, 1.12.0
> Reporter: Till Rohrmann
> Assignee: Chesnay Schepler
> Priority: Major
>
> In order to reduce the runtime dependency on Scala and also to hide the Akka
> dependency I suggest to load the AkkaRpcService and its dependencies through
> a separate class loader similar to what we do with Flink's plugins.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
