[
https://issues.apache.org/jira/browse/FLINK-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834252#comment-15834252
]
ASF GitHub Bot commented on FLINK-5527:
---------------------------------------
Github user NicoK commented on the issue:
https://github.com/apache/flink/pull/3142
Ok, let's not introduce the (now deprecated) default values in the
queryable state API.
I'll create a new Jira and PR for removing that part from the RocksDB
back-end and consistently return `null` for now (which translates to the
`UnknownKeyOrNamespace` exception).
Later we can decide to return `null` instead, if desired. Although a query
for non-existent state could be considered a failure from the point of the
queryable state API.
> 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)
