Thanks Kenn, I also think it would be nice to do away with the primitive.

On Wed, Apr 5, 2017 at 2:51 PM, Kenneth Knowles <[email protected]>
wrote:

> Yes, you have it correct. Now it is just done without a DoFn, as a
> primitive.
>
> We have some idea that we might re-add the capability; see
> https://issues.apache.org/jira/browse/BEAM-1287.
>
> Basically, it resolves around whether a window is viewed as an
> extra-special partition of a PCollection that deserves a primitive so it
> can be handled specially, versus just an implicit secondary grouping key
> that provides a GC time. I used to think the former; now I mostly think the
> latter.
>
> On Wed, Apr 5, 2017 at 12:25 PM, Thomas Weise <[email protected]> wrote:
>
> > Hi,
> >
> > As part of removing remaining OldDoFn reliance in ApexRunner I'm looking
> > for the DoFn replacement for
> > org.apache.beam.runners.core.AssignWindowsDoFn, specifically the
> > equivalent
> > of context.outputWindowedValue.
> >
> > https://github.com/apache/beam/blob/master/runners/apex/
> > src/main/java/org/apache/beam/runners/apex/translation/
> > WindowAssignTranslator.java#L52
> >
> > Looking elsewhere suggests that this isn't done using a DoFn (and reuse
> > respective execution operator)? If that's confirmed, then I can also
> create
> > a new operator for this.
> >
> > Thanks
> >
>

Reply via email to