You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Sergey Nuyanzin (Jira)" <ji...@apache.org> on 2023/02/06 12:49:00 UTC
[jira] [Updated] (FLINK-30927) Several tests started generate output with two non-abstract methods have the same parameter types, declaring type and return type
[ https://issues.apache.org/jira/browse/FLINK-30927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Nuyanzin updated FLINK-30927:
------------------------------------
Summary: Several tests started generate output with two non-abstract methods have the same parameter types, declaring type and return type (was: Several tests fail with two non-abstract methods have the same parameter types, declaring type and return type)
> Several tests started generate output with two non-abstract methods have the same parameter types, declaring type and return type
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-30927
> URL: https://issues.apache.org/jira/browse/FLINK-30927
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Reporter: Sergey Nuyanzin
> Priority: Major
>
> e.g. org.apache.flink.table.planner.runtime.stream.sql.MatchRecognizeITCase#testUserDefinedFunctions
>
> it seems during code splitter it starts generating some methods with same signature
>
> {noformat}
> org.codehaus.janino.InternalCompilerException: Compiling "MatchRecognizePatternProcessFunction$77": Two non-abstract methods "default void MatchRecognizePatternProcessFunction$77.processMatch_0(java.util.Map, org.apache.flink.cep.functions.PatternProcessFunction$Context, org.apache.flink.util.Collector) throws java.lang.Exception" have the same parameter types, declaring type and return type
> {noformat}
>
> Probably could be a side effect of https://issues.apache.org/jira/browse/FLINK-27246
--
This message was sent by Atlassian Jira
(v8.20.10#820010)