flink-issues mailing list archives

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

    I saw that deprecation but nonetheless the default value is exposed which is why a consistent
behaviour is needed.
    Since the state descriptor says "that is the value if nothing is set", I would find it
more consistent if that was true for both use cases of "state", i.e. inside an operator and
as queryable state. It would make things more complicated for users if it were only true for
the operator use, I guess.
    If the default value is not used, however, it is set to `null` internally and so `null`
is returned anyway only at the penalty of this one check that the actual value is `null`

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.

View raw message