flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-7997) Avro should be always in the user code
Date Mon, 06 Nov 2017 19:01:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-7997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Stephan Ewen resolved FLINK-7997.
    Resolution: Fixed

Fixed in c85f15ead50e9961e284eef50e5dc569560db022

> 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

View raw message