GitHub user rmetzger opened a pull request:

    https://github.com/apache/incubator-flink/pull/271

    [FLINK-610] Replace Avro with Kryo as the GenericType serializer

    This pull request is basically a collection of the work of others ;)
    @tillrohrmann contributed some of the tests (in particular for the 
serializer itself). He did the integration with 
[Chill](https://github.com/twitter/chill).
    @twalthr contributed one commit for fixing a TypeExtractor bug.
    
    I added two IT cases, checking it to work with the following types:
    
    ```java
    java.util.List<String>
    scala.math.BigInt
    java.io.File
    java.math.BigDecimal;
    java.math.BigInteger;
    java.util.HashMap;
    java.io.Serializable;
    ```
    
    I also tested it on a cluster with a Collection of Objects (containing 
Strings and Integers). It worked. I didn't test it for performance yet. The 
purpose of the pull request is to extend the type support for cases we don't 
cover by our own serialization framework.
    
    I'll now test the change with the code that brought the issue on top of my 
TODO list: 
https://issues.apache.org/jira/browse/FLINK-629?focusedCommentId=14241856&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14241856

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

    $ git pull https://github.com/rmetzger/incubator-flink flink610-master

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

    https://github.com/apache/incubator-flink/pull/271.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 #271
    
----
commit b9dac6bad47e41fc3bc1dafc3eaede1a3bf63496
Author: twalthr <[email protected]>
Date:   2014-12-10T21:02:07Z

    Fix invalid type hierarchy creation by Pojo logic

commit 64d2e52970f761ad117aec0080d0618f7f7ace95
Author: Robert Metzger <[email protected]>
Date:   2014-12-16T10:30:52Z

    [FLINK-610] Replace Avro by Kryo as the GenericType serializer
    
    The performance of data-intensive jobs using Kryo is probably going to be 
slow.

----


---
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