Hi all, BEAM-1619 is resolved. BEAM-1611 is in PR and I'll update again when it is confirmed and merged.
Kenn On Fri, Mar 3, 2017 at 10:47 AM, Thomas Groh <[email protected]> wrote: > Hey everyone; > > The submission of Surgery for the Dataflow Runner in the Java SDK has > broken all streaming jobs that use Side Inputs in that runner. > > I'm working on a fix, ETA later today. I'd like to block the release on > that. Sorry for the late notification. > > https://issues.apache.org/jira/browse/BEAM-1619 > > On Thu, Mar 2, 2017 at 10:54 PM, Jean-Baptiste Onofré <[email protected]> > wrote: > > > Hi Kenn, > > > > Fair enough. +1 > > > > Regards > > JB > > > > > > On 03/03/2017 12:28 AM, Kenneth Knowles wrote: > > > >> Hi all, > >> > >> I've just filed https://issues.apache.org/jira/browse/BEAM-1611. It is > >> technically not a bug in Beam but the easiest quick fix is to workaround > >> in > >> the DataflowRunner, so I'd like to block the release on it. It should be > >> available ahead of the release's existing schedule, and can easily be > >> cherry-picked. > >> > >> Kenn > >> > >> On Wed, Mar 1, 2017 at 10:50 PM, Jean-Baptiste Onofré <[email protected]> > >> wrote: > >> > >> Thanks Ahmet ! > >>> > >>> Regards > >>> JB > >>> > >>> On 03/02/2017 07:42 AM, Ahmet Altay wrote: > >>> > >>> Sure, I can wait. To be clear, Thursday night in which time zone? > >>>> > >>>> Thank you, > >>>> Ahmet > >>>> > >>>> On Wed, Mar 1, 2017 at 10:38 PM, Jean-Baptiste Onofré < > [email protected]> > >>>> wrote: > >>>> > >>>> Hi Ahmet, > >>>> > >>>>> > >>>>> Can you wait up to Thursday night ? Trying to merge BEAM-649. > >>>>> > >>>>> Thanks ! > >>>>> Regards > >>>>> JB > >>>>> > >>>>> > >>>>> On 03/01/2017 07:23 PM, Ahmet Altay wrote: > >>>>> > >>>>> Thank you. I will start working on it. > >>>>> > >>>>>> > >>>>>> Ahmet > >>>>>> > >>>>>> On Wed, Mar 1, 2017 at 9:03 AM, Aljoscha Krettek < > [email protected] > >>>>>> > > >>>>>> wrote: > >>>>>> > >>>>>> I just closed the last blocking issue, we should be good to go now. > >>>>>> > >>>>>> > >>>>>>> Sorry again for the hold-up. > >>>>>>> > >>>>>>> On Tue, 28 Feb 2017 at 18:38 Ahmet Altay <[email protected] > > > >>>>>>> wrote: > >>>>>>> > >>>>>>> Thank you all. I will wait for release blocking issues to be > closed. > >>>>>>> > >>>>>>> Sergio, thank you for the information. I will document the friction > >>>>>>> points > >>>>>>> during this release process. Following the release we can start a > >>>>>>> discussion about how to fix those. > >>>>>>> > >>>>>>> Ahmet > >>>>>>> > >>>>>>> On Tue, Feb 28, 2017 at 9:22 AM, Aljoscha Krettek < > >>>>>>> [email protected] > >>>>>>> > >>>>>>>> > >>>>>>>> wrote: > >>>>>>> > >>>>>>> That was my mistake, sorry for that. I should have tagged [1] as a > >>>>>>> > >>>>>>> > >>>>>>>> blocker > >>>>>>>> > >>>>>>> > >>>>>>> because leaking state is probably a bad idea. At least then people > >>>>>>> > >>>>>>>> would > >>>>>>>> > >>>>>>>> be > >>>>>>>> > >>>>>>> > >>>>>>> aware and we could have discussed whether it is a blocker. > >>>>>>> > >>>>>>>> > >>>>>>>> There is already an open PR for this now. > >>>>>>>> > >>>>>>>> [1] https://issues.apache.org/jira/browse/BEAM-1517 > >>>>>>>> > >>>>>>>> On Tue, 28 Feb 2017 at 18:21 Jean-Baptiste Onofré < > [email protected]> > >>>>>>>> > >>>>>>>> wrote: > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> Regarding BEAM-649, it's not a release blocker, it's a good to > have. > >>>>>>>> > >>>>>>>> > >>>>>>>>> As I'm pretty close to the end of the Pull Request (hopefully > >>>>>>>>> tonight > >>>>>>>>> > >>>>>>>>> or > >>>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>> tomorrow), it's a "Good To Have". > >>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>> Regards > >>>>>>>>> JB > >>>>>>>>> > >>>>>>>>> On 02/28/2017 06:09 PM, Davor Bonaci wrote: > >>>>>>>>> > >>>>>>>>> Can we please use JIRA to tag potentially release-blocking > issues? > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> Anyone > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>> can just add a 'Fix Versions' field of an open issue to the next > >>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> scheduled > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> release -- and it becomes easily visible to everyone in the > >>>>>>>>> project. > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> In general, I'm not a fan of blocking releases for new > >>>>>>>>>> functionality. > >>>>>>>>>> Rushing new features and a lack of baking time usually > translates > >>>>>>>>>> to > >>>>>>>>>> > >>>>>>>>>> bugs. > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> However, I think this time it is totally justified -- on a > separate > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> thread > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> we plan for this to be the last release before the "first stable > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> release"; > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> and picking the new features now will provide additional coverage > >>>>>>>>> for > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> it. > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>>> So, +1, but please tag in JIRA. > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> On Tue, Feb 28, 2017 at 2:09 AM, Aljoscha Krettek < > >>>>>>>>>> > >>>>>>>>>> [email protected] > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>> wrote: > >>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> I would like to finish these two: > >>>>>>>>>> > >>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-1036: Support for > new > >>>>>>>>>>> > >>>>>>>>>>> State > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> API > >>>>>>>> > >>>>>>>>> > >>>>>>>>> in FlinkRunner > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-1116: Support for > new > >>>>>>>>>>> > >>>>>>>>>>> Timer > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> API > >>>>>>>> > >>>>>>>>> > >>>>>>>>> in Flink runner > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>> Both of them are finished for the streaming runner, for the > batch > >>>>>>>>>>> > >>>>>>>>>>> runner > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> I'm merging the code for the first right now and the second will > >>>>>>>> not > >>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> take > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> long. > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>> There is also this: https://issues.apache.org/jira > >>>>>>>>>>> /browse/BEAM-1517 > >>>>>>>>>>> > >>>>>>>>>>> : > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> User > >>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>> state in the Flink Streaming Runner is not garbage collected. > It's > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>> not a > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> regression from 0.5.0 where we simply didn't have this feature > but > >>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> I'm > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> still somewhat uneasy about this. > >>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>> > >>>>>>>>>>> On Tue, 28 Feb 2017 at 09:44 Jean-Baptiste Onofré < > >>>>>>>>>>> [email protected] > >>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> wrote: > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> Fair enough. > >>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>>> I also try to merge https://github.com/apache/beam/pull/1739 > >>>>>>>>>>>> asap. > >>>>>>>>>>>> > >>>>>>>>>>>> Regards > >>>>>>>>>>>> JB > >>>>>>>>>>>> > >>>>>>>>>>>> On 02/28/2017 09:34 AM, Amit Sela wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> I'd prefer we wait to merge https://github.com/apache/ > >>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> beam/pull/2050 > >>>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> Shouldn't take long now.. > >>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> On Tue, Feb 28, 2017 at 10:00 AM Sergio Fernández < > >>>>>>>>>>>>> > >>>>>>>>>>>>> [email protected]> > >>>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> wrote: > >>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>>> Sounds good! > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>>> Ahmet, notice ASF has not current infrastructure to stage > >>>>>>>>>>>>>> Python > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Release > >>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>> Candidates. Anyway we left unmanaged the Maven deploy > lifecycle > >>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>> for > >>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>> the > >>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>> Python SDK, but it should be discussed at some point. > >>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> On Mon, Feb 27, 2017 at 11:01 PM, Ahmet Altay > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> <[email protected] > >>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>>> Hi all, > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> It's been about a month since the last release. I would > like > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> propose > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>> starting the next release. There are no releasing blocking > bugs > >>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> in > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>> JIRA > >>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>> [1]. Are there any release blocking issues I am missing? > >>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>> Unless there is an objection I will volunteer to manage this > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> release. > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>> This > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>> will be the first release with Python content. In case there > are > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> issues > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>> with that it might be easier for me to resolve and document > >>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>> those > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>> as > >>>>>>> > >>>>>>>> > >>>>>>>> part > >>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> of the release process. > >>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>>> Thank you, > >>>>>>>>>>>>>>> Ahmet > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> [1] > >>>>>>>>>>>>>>> https://issues.apache.org/jira/issues/?jql=project%20% > >>>>>>>>>>>>>>> 3D%20BEAM%20AND%20resolution%20%3D%20Unresolved%20AND% > >>>>>>>>>>>>>>> 20fixVersion%20%3D%200.6.0%20ORDER%20BY%20due%20ASC%2C% > >>>>>>>>>>>>>>> 20priority%20DESC%2C%20created%20ASC > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> -- > >>>>>>>>>>>>>> Sergio Fernández > >>>>>>>>>>>>>> Partner Technology Manager > >>>>>>>>>>>>>> Redlink GmbH > >>>>>>>>>>>>>> m: +43 6602747925 <+43%20660%202747925> > <+43%20660%202747925> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> <+43%20660%202747925> > >>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>> <+43%20660%202747925> > >>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>> e: [email protected] > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> w: http://redlink.co > >>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> -- > >>>>>>>>>>>>> > >>>>>>>>>>>> Jean-Baptiste Onofré > >>>>>>>>>>>> [email protected] > >>>>>>>>>>>> http://blog.nanthrax.net > >>>>>>>>>>>> Talend - http://www.talend.com > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> -- > >>>>>>>>>> > >>>>>>>>> Jean-Baptiste Onofré > >>>>>>>>> [email protected] > >>>>>>>>> http://blog.nanthrax.net > >>>>>>>>> Talend - http://www.talend.com > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>> -- > >>>>>> > >>>>> Jean-Baptiste Onofré > >>>>> [email protected] > >>>>> http://blog.nanthrax.net > >>>>> Talend - http://www.talend.com > >>>>> > >>>>> > >>>>> > >>>> -- > >>> Jean-Baptiste Onofré > >>> [email protected] > >>> http://blog.nanthrax.net > >>> Talend - http://www.talend.com > >>> > >>> > >> > > -- > > Jean-Baptiste Onofré > > [email protected] > > http://blog.nanthrax.net > > Talend - http://www.talend.com > > >
