beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davor Bonaci (JIRA)" <>
Subject [jira] [Commented] (BEAM-961) CountingInput could have starting number
Date Fri, 11 Nov 2016 22:30:58 GMT


Davor Bonaci commented on BEAM-961:

Just keeping the JIRA updated:

On Thu, Nov 10, 2016 at 2:02 PM, Kenneth Knowles <> wrote:

I'm not particular about whether the source itself does it versus replacing
uses of the source with a new PTransform encapsulating them. As long as
there is some object with `startingAt` and `upTo`. Either way should be
easy? Left it with starter tag as it would potentially be a fun initial
dive into the codebase.

On Thu, Nov 10, 2016 at 1:23 PM, Dan Halperin <> wrote:

> Why not support this in a follow-on pardo that shifts the range?

> CountingInput could have starting number
> ----------------------------------------
>                 Key: BEAM-961
>                 URL:
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Priority: Trivial
>              Labels: easy, newbie, starter
> TL;DR: Add {{startingAt}} to {{CountingInput}}.
> Right now you can have {{CountingInput.upTo(someNumber)}} but it came up in a test that
if you want to have, say, one PCollection that is 1 through 10 and another that is 11 through
20 - so you know they are disjoint - then it requires some boilerplate to add 10 to every
element. That boilerplate should be part of the {{CountingInput}}

This message was sent by Atlassian JIRA

View raw message