[jira] [Assigned] (FLINK-26738) Default value of StateDescriptor is valid when enable state ttl config

["Yun Tang (Jira)" <ji...@apache.org>]

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

Yun Tang reassigned FLINK-26738:
--------------------------------

    Assignee: Jianhui Dong

> Default value of StateDescriptor is valid when enable state ttl config
> ----------------------------------------------------------------------
>
>                 Key: FLINK-26738
>                 URL: https://issues.apache.org/jira/browse/FLINK-26738
>             Project: Flink
>          Issue Type: Bug
>          Components: API / Core
>    Affects Versions: 1.15.0
>            Reporter: Jianhui Dong
>            Assignee: Jianhui Dong
>            Priority: Critical
>
> Suppose we declare a ValueState like following:
> {code:java}
> ValueStateDescriptor<Tuple2<Long, Long>> descriptor =
>                 new ValueStateDescriptor<>(
>                         "average", // the state name
>                         TypeInformation.of(new TypeHint<Tuple2<Long, Long>>() {}),  
>                         Tuple2.of(0L, 0L)); 
> {code}
> and then we add state ttl config to the state:
> {code:java}
> descriptor.enableTimeToLive(StateTtlConfigUtil.createTtlConfig(60000));
> {code}
> the default value Tuple2.of(0L, 0L) will be invalid and may cause NPE.
> I don't know if this is a bug cause I see @Deprecated in the comment of the ValueStateDescriptor constructor with argument defaultValue:
> {code:java}
> Use {@link #ValueStateDescriptor(String, TypeSerializer)} instead and manually
>      *     manage the default value by checking whether the contents of the state is {@code null}.
> {code}
> and if we decide not to use the defaultValue field in the class StateDescriptor, should we add @Deprecated annotation to the field defaultValue?



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