Github user dawidwys commented on a diff in the pull request:
https://github.com/apache/flink/pull/4587#discussion_r160885887
--- Diff:
flink-libraries/flink-cep/src/main/java/org/apache/flink/cep/pattern/AndFilterFunction.java
---
@@ -1,55 +0,0 @@
-/*
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements. See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership. The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License. You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
-package org.apache.flink.cep.pattern;
-
-import org.apache.flink.api.common.functions.FilterFunction;
-
-/**
- * A filter function which combines two filter functions with a logical
and. Thus, the filter
- * function only returns true, iff both filters return true.
- *
- * @param <T> Type of the element to filter
- * @deprecated This is only used when migrating from an older Flink
version.
- * Use the {@link org.apache.flink.cep.pattern.conditions.AndCondition}
instead.
- */
-@Deprecated
-public class AndFilterFunction<T> implements FilterFunction<T> {
--- End diff --
Unfortunately bad news. As I implemented a path of migration 1.2 -> 1.3 ->
1.4. I found out we broke it with 1.4 version (I mean it is impossible to
migrate job that was first running with 1.2).
It is due to the removal of NFA#Serializer class, which was used to
serialize state in 1.2. We do not longer read or write anything there in 1.3+,
but unfortunately the serializer is needed during the initialization. Will open
a separate JIRA for that.
As for this PR, I think if we want to restore the migration path we will
need to drop those changes.
---