[
https://issues.apache.org/jira/browse/FLINK-13057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen closed FLINK-13057.
--------------------------------
> Correct comments in ListState class
> -----------------------------------
>
> Key: FLINK-13057
> URL: https://issues.apache.org/jira/browse/FLINK-13057
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends
> Reporter: Hequn Cheng
> Assignee: Hequn Cheng
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ListState can be a keyed state or an operator state, but the comment in
> ListState said it can only be a keyed stateļ¼
> {code:java}
> The state is only accessible by functions applied on a {@code KeyedStream}.
> {code}
> We can change the comment from
> {code:java}
> * <p>The state is only accessible by functions applied on a {@code
> KeyedStream}. The key is
> * automatically supplied by the system, so the function always sees the value
> mapped to the
> * key of the current element. That way, the system can handle stream and
> state partitioning
> * consistently together.{code}
> to
> {code:java}
> * <p>The state can be a keyed list state or an operator list state.
> * When it is a keyed list state, it is accessed by functions applied on a
> {@code KeyedStream}.
> * The key is automatically supplied by the system, so the function always
> sees the value mapped
> * to the key of the current element. That way, the system can handle stream
> and state
> * partitioning consistently together.
> * When it is an operator list state, the list is a collection of state items
> that are
> * independent from each other and eligible for redistribution across
> operator instances in case
> * of changed operator parallelism.
> {code}
> Appreciate any suggestions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
