beam-commits mailing list archives

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


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:
>             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(,
defaultValue)}}. It would be nice to bake this into the declaration.

This message was sent by Atlassian JIRA

View raw message