[
https://issues.apache.org/jira/browse/FLINK-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831608#comment-15831608
]
ASF GitHub Bot commented on FLINK-5527:
---------------------------------------
Github user uce commented on the issue:
https://github.com/apache/flink/pull/3142
I agree with both of your points, but I'm slightly leaning towards the side
of consistent behaviour since this behaviour is not special for queryable state
per se. It's just implementing the current contract of the state interfaces,
which still allow for a default value. Once we remove that from the state
interfaces, queryable state should also not expose it anymore, since queryable
state is registered within the program.
In the end I'm fine with both approaches and it's up to you both to decide.
:wink:
PS Note that `null` is not returned in case of a query to a non-existent
value for a key/namespace, but the `UnknownKeyOrNamespace` exception fails the
queries `Future` instance.
> 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)
