You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Steve Niemitz (Jira)" <ji...@apache.org> on 2022/01/17 16:09:00 UTC

[jira] [Created] (BEAM-13672) Window.into() without a windowFn not correctly translated to portable representation

Steve Niemitz created BEAM-13672:
------------------------------------

             Summary: Window.into() without a windowFn not correctly translated to portable representation
                 Key: BEAM-13672
                 URL: https://issues.apache.org/jira/browse/BEAM-13672
             Project: Beam
          Issue Type: Bug
          Components: sdk-java-core
    Affects Versions: 2.35.0
            Reporter: Steve Niemitz


On the "classic" non-portable runner, you can do something like:

{{Window.configure().discardingFiredPanes().withAllowedLateness(maxFinalJitter)}}

to configure the max allowed lateness on a PCollection.  This translates into a Flatten transform [1].  It doesn't seem like the FlattenTranslator uses this information anywhere [2], and the result is that the configuration is lost when translating to a portable pipeline.

[1] [https://github.com/apache/beam/blob/master/sdks/java/core/src/main/java/org/apache/beam/sdk/transforms/windowing/Window.java#L403]

 

[2] https://github.com/apache/beam/blob/master/runners/core-construction-java/src/main/java/org/apache/beam/runners/core/construction/FlattenTranslator.java#L53



--
This message was sent by Atlassian Jira
(v8.20.1#820001)