[jira] [Commented] (BEAM-961) CountingInput could have starting number

["Davor Bonaci (JIRA)" <ji...@apache.org>]

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

Davor Bonaci commented on BEAM-961:
-----------------------------------

Just keeping the JIRA updated:

On Thu, Nov 10, 2016 at 2:02 PM, Kenneth Knowles <kl...@google.com.invalid> 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 <dh...@google.com> wrote:

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

> CountingInput could have starting number
> ----------------------------------------
>
>                 Key: BEAM-961
>                 URL: https://issues.apache.org/jira/browse/BEAM-961
>             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
(v6.3.4#6332)