beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1335) ValueState could use an initial/default value
Date Wed, 01 Feb 2017 03:21:52 GMT

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

Kenneth Knowles commented on BEAM-1335:
---------------------------------------

That is a valid point. We dealt with about the same issue with the in-memory {{Source}} that
is part of the {{Create}} transform. It is a requirement that we must operate successfully
with elements that are not Java {{Serializable}}. So it takes some implementation, but I think
once it is done the interface remains the same. Did you hit a point where you had to enlarge
a user-facing API or anything like that?

> ValueState could use an initial/default value
> ---------------------------------------------
>
>                 Key: BEAM-1335
>                 URL: https://issues.apache.org/jira/browse/BEAM-1335
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Priority: Minor
>              Labels: starter
>
> In writing example state code with {{ValueState}} there is almost always a use of {{firstNonNull(state.read(),
defaultValue)}}. It would be nice to bake this into the declaration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message