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

Flink Jira Bot updated FLINK-16310:
-----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned 
 (was: auto-deprioritized-major auto-unassigned stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any 
updates so it is being deprioritized. If this ticket is actually Minor, please 
raise the priority and ask a committer to assign you the issue or revive the 
public discussion.


> Javadoc of AppendingState.get() contradicts with behavior of 
> UserFacingListState
> --------------------------------------------------------------------------------
>
>                 Key: FLINK-16310
>                 URL: https://issues.apache.org/jira/browse/FLINK-16310
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation, Runtime / State Backends
>    Affects Versions: 1.6.4, 1.7.2, 1.8.3, 1.9.2, 1.10.0
>            Reporter: Tzu-Li (Gordon) Tai
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, 
> auto-unassigned
>
> The {{get()}} method on the user-facing state handle interface 
> {{AppendingState}} states that:
> {code}
> @return The operator state value corresponding to the current input or NULL 
> if the state is empty.
> {code}
> This behavior, is not true for the user-facing list state handles, as the 
> behavior has always been that if the list state does not have elements, an 
> empty list is returned (see FLINK-4307 / {{UserFacingListState}}).
> The fix would be to only mention the null-returning behavior on the internal 
> list state interface, i.e. {{InternalListState}}, and fix the Javadoc for 
> {{AppendingState}}.



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

Reply via email to