[
https://issues.apache.org/jira/browse/FLINK-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826424#comment-15826424
]
ASF GitHub Bot commented on FLINK-5527:
---------------------------------------
GitHub user NicoK opened a pull request:
https://github.com/apache/flink/pull/3142
[FLINK-5527][query] querying a non-existing key does not return the default
value
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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NicoK/flink flink-5527
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3142.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3142
----
commit 0d7c5f3ebf3a721b679cf830b124ffd4d646c8f6
Author: Nico Kruber <n...@data-artisans.com>
Date: 2017-01-17T13:26:16Z
[FLINK-5527][query] querying a non-existing key does not return the default
value
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.
----
> 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)
