beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <>
Subject [jira] [Commented] (BEAM-1346) Drop Late Data in ReduceFnRunner
Date Mon, 13 Feb 2017 21:16:41 GMT


Kenneth Knowles commented on BEAM-1346:

I agree with your paranoia. This is related to BEAM-696. I think {{PushbackSideInputRunner}}
is technically OK because it pushes all the complexity to the runner. The runner can provide
a {{ReadyCheckingSideInputReader}} that understands the merging, and the runner decides when
to wake up the processing and feed the pushed-back elements, so it can alter its timers, etc,
according to merging. And if this is all too complex, maybe the runner can [disable any troublesome
for now.

> Drop Late Data in ReduceFnRunner
> --------------------------------
>                 Key: BEAM-1346
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core
>    Affects Versions: 0.5.0
>            Reporter: Aljoscha Krettek
> I think these two commits recently broke late-data dropping for the Flink Runner (and
maybe for other runners as well):
> -
> -
> It boils down to the {{LateDataDroppingDoFnRunner}} not being used anymore  because {{DoFnRunners.lateDataDroppingRunner()}}
is not called anymore when a {{DoFn}} is a {{ReduceFnExecutor}} (because that interface was
> Maybe we should think about dropping late data in another place, my suggestion is {{ReduceFnRunner}}
but that's open for discussion.

This message was sent by Atlassian JIRA

View raw message