You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2016/07/18 12:09:20 UTC

[jira] [Resolved] (FLINK-4149) Fix Serialization of NFA in AbstractKeyedCEPPatternOperator

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

Aljoscha Krettek resolved FLINK-4149.
-------------------------------------
    Resolution: Fixed

Done in https://github.com/apache/flink/commit/ac06146719e1061aecdc7f18c95913ac9009a711

> Fix Serialization of NFA in AbstractKeyedCEPPatternOperator
> -----------------------------------------------------------
>
>                 Key: FLINK-4149
>                 URL: https://issues.apache.org/jira/browse/FLINK-4149
>             Project: Flink
>          Issue Type: Bug
>          Components: CEP
>    Affects Versions: 1.0.0, 1.1.0, 1.0.1, 1.0.2, 1.0.3
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Blocker
>             Fix For: 1.1.0
>
>
> A job that uses CEP fails upon restore with a {{NullPointerException}} in {{NFA.process()}}. The reason seems to be that field {{computationStates}} is {{null}}. This field is transient and read in a custom {{readObject()}} method.
> In {{AbstractKeyedCEPPatternOperator}} this snipped is used to construct a {{StateDescriptor}} for an {{NFA}} state:
> {code}
> new ValueStateDescriptor<NFA<IN>>(
>     NFA_OPERATOR_STATE_NAME,
>     new KryoSerializer<NFA<IN>>((Class<NFA<IN>>) (Class<?>) NFA.class, getExecutionConfig()),
>     null)
> {code}
> It seems Kryo does not invoke {{readObject}}/{{writeObject}}. We probably need a custom {{TypeSerializer}} for {{NFA}} to solve the problem.



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