GitHub user NicoK opened a pull request:
https://github.com/apache/flink/pull/3193
[FLINK-5527][query] querying a non-existing key is inconsistent among state
backends
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 but results in the default
value
if RocksDBStateBackend is set.
This removes the special handling from the RocksDBStateBackend and makes it
consistent with the other two back-ends, i.e. returning null which results
in the mentioned UnknownKeyOrNamespace exception.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NicoK/flink flink-5613
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3193.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 #3193
----
commit a767d4ec9e855558c39d3902fc633b331fb64163
Author: Nico Kruber <[email protected]>
Date: 2017-01-17T13:26:16Z
[FLINK-5527][query] querying a non-existing key is inconsistent among state
backends
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 but results in the default
value
if RocksDBStateBackend is set.
This removes the special handling from the RocksDBStateBackend and makes it
consistent with the other two back-ends, i.e. returning null which results
in the mentioned UnknownKeyOrNamespace exception.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
