[
https://issues.apache.org/jira/browse/FLINK-10903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693574#comment-16693574
]
Luka Jurukovski commented on FLINK-10903:
-----------------------------------------
Thanks for the in depth response!
*Akka* *Shading*
I wasn't aware of the complexities of shading Akka in that regard. I just
assumed that it would be equivalent to shading other dependencies with some
added complexity around how Akka merges reference.conf files. Out of curiosity
I'll try to do some more digging around this.
*Updating the Akka version*
This is very good to know, I was a little concerned/curious due to the fact
that I believe the version that is being used (if I remember correctly) is the
oldest version that Akka will support, which is likely to fall away in the
relatively near future.
*Child-first classloading*
I think I need to re-explore this option in my project, at the time that I
disabled Child-First classloading I was still new to Flink in general. However,
per the Flink documentation, there may be instances in which users might be
forced to use parent first loading.
*Hiding Akka in Runtime*
This seems like this would solve my use case. Can you point me to the ticket
with the relevant investigations, so I can add myself as a watcher? I think
with this I can close the ticket, and if I find anything related to *Akka
Shading* option I can comment there as an alternative if this methodology runs
into issues?
> Shade Internal Akka Dependencies
> --------------------------------
>
> Key: FLINK-10903
> URL: https://issues.apache.org/jira/browse/FLINK-10903
> Project: Flink
> Issue Type: Wish
> Reporter: Luka Jurukovski
> Priority: Minor
>
> Akka is not a publicly exposed API but is something that forces developers
> (particularly in Scala) to use an older version. It would be nice if this was
> shaded so that developers are free to use the version of their choosing
> without needing to worry about binary backwards compatibility, or in the case
> that a user is forced to use parent first classloading
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
