flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From uce <...@git.apache.org>
Subject [GitHub] flink issue #3142: [FLINK-5527][query] querying a non-existing key does not ...
Date Fri, 20 Jan 2017 11:57:55 GMT
Github user uce commented on the issue:

    https://github.com/apache/flink/pull/3142
  
    I agree with both of your points, but I'm slightly leaning towards the side of consistent
behaviour since this behaviour is not special for queryable state per se. It's just implementing
the current contract of the state interfaces, which still allow for a default value. Once
we remove that from the state interfaces, queryable state should also not expose it anymore,
since queryable state is registered within the program.
    
    In the end I'm fine with both approaches and it's up to you both to decide. :wink:
    
    PS Note that `null` is not returned in case of a query to a non-existent value for a key/namespace,
but the `UnknownKeyOrNamespace` exception fails the queries `Future` instance.



---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message