You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2017/11/06 13:41:00 UTC

[jira] [Created] (FLINK-7997) Avro should be always in the user code

Stephan Ewen created FLINK-7997:
-----------------------------------

             Summary: 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)