flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5527) QueryableState: requesting a non-existing key in MemoryStateBackend or FsStateBackend does not return the default value
Date Fri, 20 Jan 2017 10:45:27 GMT

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

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

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/3142
  
    The default value so far referred to access to the state object from within a program.
    I would avoid extending this definition to queryable state given that we are deprecating
it.
    
    If we clearly spell the behavior out, I see no problem that queryable state access does
not use the default value.


> QueryableState: requesting a non-existing key in MemoryStateBackend or FsStateBackend
does not return the default value
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-5527
>                 URL: https://issues.apache.org/jira/browse/FLINK-5527
>             Project: Flink
>          Issue Type: Improvement
>          Components: Queryable State
>    Affects Versions: 1.2.0
>            Reporter: Nico Kruber
>            Assignee: Nico Kruber
>
> Querying for a non-existing key for a state that has a default value set currently results
in an UnknownKeyOrNamespace exception when the MemoryStateBackend or FsStateBackend is used.
It should return the default value instead just like the RocksDBStateBackend.



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

Mime
View raw message