flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5527) QueryableState: requesting a non-existing key in MemoryStateBackend or FsStateBackend does not return the default value
Date Mon, 23 Jan 2017 15:11:26 GMT

    [ https://issues.apache.org/jira/browse/FLINK-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834715#comment-15834715
] 

ASF GitHub Bot commented on FLINK-5527:
---------------------------------------

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 <nico@data-artisans.com>
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.

----


> 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)

Mime
View raw message