beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (BEAM-230) Remove WindowedValue#valueInEmptyWindows
Date Thu, 18 May 2017 18:48:05 GMT

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

Daniel Halperin closed BEAM-230.
--------------------------------
    Resolution: Won't Fix

I believe this is now a WontFix issue as the first stable release went out with this functionality
still implemented, and no one is operating on it.

[I may be wrong -- the functionality is deprecated, so we could remove it... but still used
I believe. If so, please reopen and explain.]

> Remove WindowedValue#valueInEmptyWindows
> ----------------------------------------
>
>                 Key: BEAM-230
>                 URL: https://issues.apache.org/jira/browse/BEAM-230
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Thomas Groh
>              Labels: backward-incompatible
>             Fix For: Not applicable
>
>
> A WindowedValue in no windows does not exist, and can be dropped by a runner at any time.
> We should also assert that any collection of windows is nonempty when creating a new
WindowedValue. If a user wants to drop an element, they should explicitly filter it out rather
than expecting it to be dropped by the runner.



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

Mime
View raw message