[ 
https://issues.apache.org/jira/browse/FLINK-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545395#comment-14545395
 ] 

ASF GitHub Bot commented on FLINK-2019:
---------------------------------------

GitHub user rmetzger opened a pull request:

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

    [FLINK-2019] Use a properly instantiated Kryo in the GenericTypeComparator

    I'll merge this once travis is green.

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

    $ git pull https://github.com/rmetzger/flink flink2019

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

    https://github.com/apache/flink/pull/679.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 #679
    
----
commit b2c514a2bb9b49a3bb4b00604985c145a66369f3
Author: Robert Metzger <rmetz...@apache.org>
Date:   2015-05-15T11:48:49Z

    [FLINK-2019] Use a properly instantiated Kryo in the GenericTypeComparator

----


> Grouping by Joda DateTime field fails with Kryo exception
> ---------------------------------------------------------
>
>                 Key: FLINK-2019
>                 URL: https://issues.apache.org/jira/browse/FLINK-2019
>             Project: Flink
>          Issue Type: Improvement
>          Components: Type Serialization System
>    Affects Versions: 0.9
>            Reporter: Robert Metzger
>            Assignee: Robert Metzger
>
> Running
> {code}
> DataSet<Tuple3<String, Integer, DateTime>> counts =
> text.flatMap(new LineSplitter()).groupBy(0, 2).sum(1);
> {code}
> fails with
> {code}
> com.esotericsoftware.kryo.KryoException: Class cannot be created (missing 
> no-arg constructor): org.joda.time.chrono.ISOChronology
> Serialization trace:
> iChronology (org.joda.time.DateTime)
>       at 
> com.esotericsoftware.kryo.Kryo$DefaultInstantiatorStrategy.newInstantiatorOf(Kryo.java:1228)
>       at com.esotericsoftware.kryo.Kryo.newInstantiator(Kryo.java:1049)
>       at com.esotericsoftware.kryo.Kryo.newInstance(Kryo.java:1058)
>       at 
> com.esotericsoftware.kryo.serializers.FieldSerializer.createCopy(FieldSerializer.java:620)
>       at 
> com.esotericsoftware.kryo.serializers.FieldSerializer.copy(FieldSerializer.java:624)
>       at com.esotericsoftware.kryo.Kryo.copy(Kryo.java:862)
>       at 
> com.esotericsoftware.kryo.serializers.ObjectField.copy(ObjectField.java:140)
>       at 
> com.esotericsoftware.kryo.serializers.FieldSerializer.copy(FieldSerializer.java:634)
>       at com.esotericsoftware.kryo.Kryo.copy(Kryo.java:862)
>       at 
> org.apache.flink.api.java.typeutils.runtime.GenericTypeComparator.setReference(GenericTypeComparator.java:77)
>       at 
> org.apache.flink.api.java.typeutils.runtime.GenericTypeComparator.setReference(GenericTypeComparator.java:36)
>       at 
> org.apache.flink.api.java.typeutils.runtime.TupleComparator.setReference(TupleComparator.java:72)
>       at 
> org.apache.flink.api.java.typeutils.runtime.TupleComparator.setReference(TupleComparator.java:30)
>       at 
> org.apache.flink.runtime.util.NonReusingKeyGroupedIterator.nextKey(NonReusingKeyGroupedIterator.java:115)
>       at 
> org.apache.flink.runtime.operators.chaining.SynchronousChainedCombineDriver.sortAndCombine(SynchronousChainedCombineDriver.java:233)
>       at 
> org.apache.flink.runtime.operators.chaining.SynchronousChainedCombineDriver.close(SynchronousChainedCombineDriver.java:194)
>       at 
> org.apache.flink.runtime.operators.chaining.ChainedFlatMapDriver.close(ChainedFlatMapDriver.java:87)
>       at 
> org.apache.flink.runtime.operators.DataSourceTask.invoke(DataSourceTask.java:189)
>       at org.apache.flink.runtime.taskmanager.Task.run(Task.java:562)
>       at java.lang.Thread.run(Thread.java:745)
> {code}
> The issue has been reported by [~f.pompermaier]: 
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/KryoException-with-joda-Datetime-td1248.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to