Just to be clear on the CassandraIO issues: they are not regression (it was like this since the addition of the CassandraIO), they are not data loss. I consider as a bug/improvement as the read is performed on a single worker (the split returns always 1).
As said, I gonna work today on those issues as a best effort. However, I keep the release cut "deadline" to tonight/tomorrow early morning my time. Regards JB On 01/26/2018 06:33 AM, Reuven Lax wrote: > I agree - if CassandraIO issues are not regressions (and are not critical > data-loss bugs), I don't think the release should block on it. > > Reuven > > On Thu, Jan 25, 2018 at 9:07 PM, Jean-Baptiste Onofré <j...@nanthrax.net > <mailto:j...@nanthrax.net>> wrote: > > I disagree: the CassandraIO issues are not blocker as they are not > regression. > > In order to insure the release pace, I will go forward, these issues will > be fix > for the next release cycle. > > For the blog, it's up to you. However, with the next release pace we do, > I'm not > sure it makes sense to do it for each release. > > We still have a full day before the release cut. So, let me do my best on > the > CassandraIO issues, as a best effort. But let's target to cut the release > tonight/tomorrow early morning as planned. > > Regards > JB > > On 01/25/2018 09:56 PM, Ismaël Mejía wrote: > > I saw some recent reports on issues with CassandraIO that are not > > blockers (not data loss) but IMO deserve to be included because > > basically the issues imply that users cannot read from Cassandra in > > parallel, and they were reported by production users. Probably a good > > idea to finish these before the cut (they don't seem really hard to > > fix), even if this implies to move the release cut one or two days. > > > > I also would like to volunteer to write the release blog post in > > particular I would like to add a new section to thank the people that > > contributed in this release as other projects do. > > > > On Thu, Jan 25, 2018 at 9:08 PM, Reuven Lax <re...@google.com > <mailto:re...@google.com>> wrote: > >> Thank you for running this JB! > >> > >> On Thu, Jan 25, 2018 at 11:50 AM, Jean-Baptiste Onofré > <j...@nanthrax.net > <mailto:j...@nanthrax.net>> > >> wrote: > >>> > >>> Hi guys, > >>> > >>> Kenn and I are doing the latest triage. I'm creating some PRs that > would > >>> be good > >>> for 2.3.0 (but not blocker). > >>> > >>> As discussed, I plan to start the release process tomorrow evening (my > >>> time). > >>> > >>> Thanks ! > >>> Regards > >>> JB > >>> > >>> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote: > >>>> Hi guys, > >>>> > >>>> Some days ago, I proposed to start Beam 2.3.0 around January 26th. > So, > >>>> we are > >>>> few days from this date. > >>>> > >>>> As a best effort, can you please in Jira flag the Jira with fix > version > >>>> 2.3.0 > >>>> and blocker for the release. Then, I will know when I can start the > >>>> release process. > >>>> > >>>> Thanks ! > >>>> > >>>> Regards > >>>> JB > >>>> > >>> > >>> -- > >>> Jean-Baptiste Onofré > >>> jbono...@apache.org <mailto:jbono...@apache.org> > >>> http://blog.nanthrax.net > >>> Talend - http://www.talend.com > >> > >> > > -- > Jean-Baptiste Onofré > jbono...@apache.org <mailto:jbono...@apache.org> > http://blog.nanthrax.net > Talend - http://www.talend.com > > -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
