GitHub user fhueske opened a pull request:

    https://github.com/apache/flink/pull/1330

    [FLINK-2940] [JavaAPI] Remove Chill dependency from flink-java.

    This PR replaces `flink-java`'s `chill` dependency by `chill-java` to 
decouple `flink-java` from Scala.
    Chill is used within the `KryoSerializer` to obtain a "Scala-preconfigured" 
Kryo instance. Hence, Chill is still required for Scala DataSet or DataStream 
programs. Separate KryoSerializers for Scala and Java are hard to provide, 
because `GenericTypeInformation` can be generated through the `TypeExtractor`, 
`TypeParser`, and the Scala compiler marko. 
    
    In this PR, the `KryoSerializer` tries to dynamically load Chill's 
`ScalaKryoInstantiator` and generate a Kryo instance through reflection to 
circumvent the Chill dependency. As a fallback, a regular Kryo instance is 
created. Consequently, Chill's Kryo instance is used whenever Chill is present 
in the classpath. To ensure that client, JM, and TM have Chill in their 
classpath, we add Chill as a dependency to `flink-client`.
    
    **Note**: Before merging, we need to check if this works for Java and Scala 
programs which are submitted to a cluster (including some collection data 
sources which are serialized at the client).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/fhueske/flink scalaFlinkJava

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/1330.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1330
    
----
commit 9b3b86fb8bbd1d36914b1f13519e314090ce9deb
Author: Fabian Hueske <[email protected]>
Date:   2015-11-03T15:57:49Z

    [FLINK-2940] [JavaAPI] Remove Chill dependency from flink-java.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to