[
https://issues.apache.org/jira/browse/FLINK-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827901#comment-15827901
]
ASF GitHub Bot commented on FLINK-5527:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3142
In a separate change, we actually deprecated the default value in states.
It does not behave very well at runtime in many cases and we thought that it
would be simpler to let the user code handle default values.
Can queryable state not simply return null as well? I am also not sure if
the assumption can be made that external queries want the same default value as
the state updating code paths (which frequently use the default value only as a
shortcut for initializing the state).
> 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)
