You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yun Tang (Jira)" <ji...@apache.org> on 2022/04/08 14:04:00 UTC

[jira] [Resolved] (FLINK-26852) RocksDBMapState#clear not forwarding exceptions

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

Yun Tang resolved FLINK-26852.
------------------------------
    Fix Version/s: 1.16.0
       Resolution: Fixed

merged in master: 241e819d82bf84535b355e3822894d6b685db0a5

> RocksDBMapState#clear not forwarding exceptions
> -----------------------------------------------
>
>                 Key: FLINK-26852
>                 URL: https://issues.apache.org/jira/browse/FLINK-26852
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / State Backends
>    Affects Versions: 1.15.0, 1.14.4
>            Reporter: Nico Kruber
>            Assignee: Hangxiang Yu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.16.0
>
>
> I accidentally found an inconsistent behaviour in the RocksDB state backend implementation:
> If there's an exception in {{AbstractRocksDBState#clear()}} it will forward that inside a {{FlinkRuntimeException}}.
> However, if there's an exception in {{RocksDBMapState#clear}} it will merely print the exception stacktrace and continue as is.
> I assume, forwarding the exception as {{FlinkRuntimeException}} should be the desired behaviour for both use cases...



--
This message was sent by Atlassian Jira
(v8.20.1#820001)