beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Commented] (BEAM-638) Add a Window function to create a bounded PCollection from an unbounded one
Date Mon, 03 Oct 2016 10:50:20 GMT

    [ https://issues.apache.org/jira/browse/BEAM-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542121#comment-15542121
] 

Jean-Baptiste Onofré commented on BEAM-638:
-------------------------------------------

Let me explain a bit what I have in mind. Actually, all IO write implemented with {{DoFn}}
will work with an unbounded collection. The problem is more for the {{TextIO.Write}}.
Generally speaking, my concern is that using a Window on an unbounded PCollection is still
an unbounded PCollection: some user may expect to have a bounded PCollection for the Window.

So, we have three points to address:
1. The Sink (and generally speaking the IO write) should be able to deal with unbounded PCollection
2. A Window on an unbounded PCollection could result on a bounded collection (and not a chunk
of the unbounded collection)

Thoughts ?

> Add a Window function to create a bounded PCollection from an unbounded one
> ---------------------------------------------------------------------------
>
>                 Key: BEAM-638
>                 URL: https://issues.apache.org/jira/browse/BEAM-638
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-core
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Davor Bonaci
>
> Today, if the pipeline source is unbounded, and the sink expects a bounded collection,
there's no way to use a single pipeline. Even a window creates a chunk on the unbounded PCollection,
but the "sub" PCollection is still unbounded.
> It would be helpful for users to have a Window function that create a bounded PCollection
(on the window) from an unbounded PCollection coming from the source.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message