[ https://issues.apache.org/jira/browse/FLINK-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated FLINK-10391: --------------------------- Description: >From the JodaLocalTimeSerializer#write, we serialize getMillisOfDay() value >from LocalTime. For read method: {code} final int time = input.readInt(true); return new LocalTime(time, ISOChronology.getInstanceUTC().withZone(DateTimeZone.UTC)); {code} It seems http://joda-time.sourceforge.net/apidocs/org/joda/time/LocalTime.html#fromMillisOfDay(long,%20org.joda.time.Chronology) should be used instead. was: >From the JodaLocalTimeSerializer#write, we serialize getMillisOfDay() value >from LocalTime. For read method: {code} final int time = input.readInt(true); return new LocalTime(time, ISOChronology.getInstanceUTC().withZone(DateTimeZone.UTC)); {code} It seems http://joda-time.sourceforge.net/apidocs/org/joda/time/LocalTime.html#fromMillisOfDay(long,%20org.joda.time.Chronology) should be used instead. > MillisOfDay is used in place of instant for LocalTime ctor in > AvroKryoSerializerUtils > ------------------------------------------------------------------------------------- > > Key: FLINK-10391 > URL: https://issues.apache.org/jira/browse/FLINK-10391 > Project: Flink > Issue Type: Bug > Reporter: Ted Yu > Priority: Minor > > From the JodaLocalTimeSerializer#write, we serialize getMillisOfDay() value > from LocalTime. > For read method: > {code} > final int time = input.readInt(true); > return new LocalTime(time, > ISOChronology.getInstanceUTC().withZone(DateTimeZone.UTC)); > {code} > It seems > http://joda-time.sourceforge.net/apidocs/org/joda/time/LocalTime.html#fromMillisOfDay(long,%20org.joda.time.Chronology) > should be used instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)