Re: [DISCUSS] [BEAM-438] Rename one of PTransform.apply or PInput.apply

2016-12-08 Thread Kenneth Knowles
Hi users@, This has been done, and will show up in the next incubating release. Kenn On Wed, Dec 7, 2016 at 5:13 PM, Ben Chambers wrote: > +1 to pushing all remaining "major" (read likely to affect everyone) breaks > through in a single release. > > On Wed, Dec

Re: [DISCUSS] [BEAM-438] Rename one of PTransform.apply or PInput.apply

2016-12-07 Thread Ben Chambers
+1 to pushing all remaining "major" (read likely to affect everyone) breaks through in a single release. On Wed, Dec 7, 2016 at 3:56 PM Dan Halperin wrote: > +user@, because this is a user-impacting change and they might not all be > paying attention to the dev@

Re: [DISCUSS] [BEAM-438] Rename one of PTransform.apply or PInput.apply

2016-12-07 Thread Dan Halperin
+user@, because this is a user-impacting change and they might not all be paying attention to the dev@ list. +1 I'm mildly reluctant because this will break all users that have written composite transforms -- and I'm the jerk that filed the issue (a few times now, on different iterations of the