You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Nico Kruber (JIRA)" <ji...@apache.org> on 2017/01/23 10:55:26 UTC

[jira] [Updated] (FLINK-5613) QueryableState: requesting a non-existing key in RocksDBStateBackend is not consistent with the MemoryStateBackend and FsStateBackend

     [ https://issues.apache.org/jira/browse/FLINK-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nico Kruber updated FLINK-5613:
-------------------------------
    Description: 
Querying for a non-existing key for a state that has a default value set currently results in the default value being returned in the RocksDBStateBackend only. MemoryStateBackend or FsStateBackend will return null which results in an UnknownKeyOrNamespace exception.

Default values are now deprecated and will be removed eventually so we should not introduce them into the new queryable state API and thus adapt the RocksDBStateBackend accordingly.

This refers to FLINK-5527 but solves the initial issues the opposite way.

  was:
Querying for a non-existing key for a state that has a default value set currently results in the default value being returned in the RocksDBStateBackend only. MemoryStateBackend or FsStateBackend will return null which results in an UnknownKeyOrNamespace exception.

Default values are now deprecated and will be removed eventually so we should not introduce them into the new queryable state API and thus adapt the RocksDBStateBackend accordingly


> QueryableState: requesting a non-existing key in RocksDBStateBackend is not consistent with the MemoryStateBackend and FsStateBackend
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-5613
>                 URL: https://issues.apache.org/jira/browse/FLINK-5613
>             Project: Flink
>          Issue Type: Bug
>          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 the default value being returned in the RocksDBStateBackend only. MemoryStateBackend or FsStateBackend will return null which results in an UnknownKeyOrNamespace exception.
> Default values are now deprecated and will be removed eventually so we should not introduce them into the new queryable state API and thus adapt the RocksDBStateBackend accordingly.
> This refers to FLINK-5527 but solves the initial issues the opposite way.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)