You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2017/11/07 13:31:00 UTC
[jira] [Commented] (FLINK-7997) Avro should be always in the user
code
[ https://issues.apache.org/jira/browse/FLINK-7997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241991#comment-16241991 ]
Chesnay Schepler commented on FLINK-7997:
-----------------------------------------
So we always assume that avro users add flink-avro to their jar? Could we then remove flink-avro from flink-dist (and by extension, avro and codehaus.jackson)?
> Avro should be always in the user code
> --------------------------------------
>
> Key: FLINK-7997
> URL: https://issues.apache.org/jira/browse/FLINK-7997
> Project: Flink
> Issue Type: Improvement
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Fix For: 1.4.0
>
>
> Having Avro in the user code space makes it possible for users to use different Avro versions that the ones pulled in by an overloaded classpath (for example when having Hadoop in the classpath)
> This is possible through the new child-first classloading in Flink 1.4.
> Also, this should fix the problem of "X cannot be cast to X", because Avro classes will be scoped to the user code class loader, and the Avro schema cache will not be JVM-wide-
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)