[jira] [Updated] (FLINK-2236) RowSerializer and CaseClassComparator are not in sync regarding Null-Values

["Aljoscha Krettek (JIRA)" <ji...@apache.org>]

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

Aljoscha Krettek updated FLINK-2236:
------------------------------------
    Priority: Blocker  (was: Major)

> RowSerializer and CaseClassComparator are not in sync regarding Null-Values
> ---------------------------------------------------------------------------
>
>                 Key: FLINK-2236
>                 URL: https://issues.apache.org/jira/browse/FLINK-2236
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Aljoscha Krettek
>            Priority: Blocker
>
> The RowSerializer was recently updated to allow it to handle null values. This changes the binary layout of the serialised data. CaseClassComparator, which is used for comparison, is not aware of this new layout and therefore fails. The problem only occurs when a key is long enough to exceed the normalised-key length, that's why the tests fail to notice the bug.
> I think the solution is to modify all Tuple-like serializers/comparators (TupleComparatorBase, CaseClassComparator, TupleSerializer, CaseClassSerializer, RowSerializer) to handle null-values, thus bringing the binary format in sync again.



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