+1, maybe call them "typed." (And for many transforms, the unbound versions need not exist, so we wouldn't even need the distinction...) On Feb 18, 2016 8:38 AM, "Dan Halperin" <[email protected]> wrote:
> What Ben said is true .... but I'd be in favor of renaming or removing > these constructs once we can make backwards-incompatible changes ;) > > On Thu, Feb 18, 2016 at 8:31 AM, Ben Chambers <[email protected] > > > wrote: > > > Classes named "Bound" are used throughout the sdk to describe builders > that > > are specified enough to be applied. It indicates that the required > > parameters have been bound. It is not related to whether the output > > PCollection is bounded or unbounded. > > > > On Thu, Feb 18, 2016, 7:42 AM bakey pan <[email protected]> wrote: > > > > > Hi,all: > > > I notice that in in the PubSubIO class, there only exist one Bound > > > static class inherit from PTransform. > > > But actually in the apply method of Bound,whether return a bounded > or > > > unbounded PCollection is depend on the variables maxNumRecords and > > > maxReadTime.So why not name this class "MixBound" or else. > > > I think that is a little bit confuse name it "Bound" but actually > > it > > > can be unbouned data stream > > > > > > -- > > > Best Regards > > > BakeyPan > > > > > >
