[ 
https://issues.apache.org/jira/browse/FLINK-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687289#comment-15687289
 ] 

ASF GitHub Bot commented on FLINK-5023:
---------------------------------------

Github user aljoscha commented on a diff in the pull request:

    https://github.com/apache/flink/pull/2768#discussion_r89161821
  
    --- Diff: 
flink-streaming-java/src/main/java/org/apache/flink/streaming/api/operators/AbstractStreamOperator.java
 ---
    @@ -487,7 +487,7 @@ protected ProcessingTimeService 
getProcessingTimeService() {
         * @throws IllegalStateException Thrown, if the key/value state was 
already initialized.
         * @throws Exception Thrown, if the state backend cannot create the 
key/value state.
         */
    -   protected <S extends State> S getPartitionedState(StateDescriptor<S, ?> 
stateDescriptor) throws Exception {
    +   protected <V, S extends State<V>> S 
getPartitionedState(StateDescriptor<S> stateDescriptor) throws Exception {
    --- End diff --
    
    Here, the same thing I mentioned on `KeyedStateBackend` holds, we don't 
need the additional `V` parameter.


> Add get() method in State interface
> -----------------------------------
>
>                 Key: FLINK-5023
>                 URL: https://issues.apache.org/jira/browse/FLINK-5023
>             Project: Flink
>          Issue Type: Improvement
>          Components: State Backends, Checkpointing
>            Reporter: Xiaogang Shi
>            Assignee: Xiaogang Shi
>
> Currently, the only method provided by the State interface is `clear()`. I 
> think we should provide another method called `get()` to return the 
> structured value (e.g., value, list, or map) under the current key. 
> In fact, the functionality of `get()` has already been implemented in all 
> types of states: e.g., `value()` in ValueState and `get()` in ListState. The 
> modification to the interface can better abstract these states.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to