flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flink Jira Bot (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-5373) Extend Unit Tests for StateAssignmentOperation
Date Wed, 16 Jun 2021 10:42:02 GMT

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

Flink Jira Bot updated FLINK-5373:
    Labels: auto-unassigned stale-major  (was: auto-unassigned)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community
manage its development. I see this issues has been marked as Major but is unassigned and neither
itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major"
to the issue". If this ticket is a Major, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be deprioritized.

> Extend Unit Tests for StateAssignmentOperation
> ----------------------------------------------
>                 Key: FLINK-5373
>                 URL: https://issues.apache.org/jira/browse/FLINK-5373
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / State Backends
>            Reporter: Aljoscha Krettek
>            Priority: Major
>              Labels: auto-unassigned, stale-major
> The legacy savepoint restore end-to-end test uncovered a slight problem with null pointers
that is fixed by this commit: https://github.com/apache/flink/commit/74df7631316e78af39a5416e12c1adc8a46d87fe
> We should extend unit tests to catch this case in the future.

This message was sent by Atlassian Jira

View raw message