There has been an issue about this for a while now: https://issues.apache.org/jira/browse/BEAM-234
On Fri, 17 Jun 2016 at 09:55 Jean-Baptiste Onofré <[email protected]> wrote: > Hi Ismaël, > > I didn't talk a change between Dataflow SDK and Beam, I'm talking about > a change between two Beam SNAPSHOTs ;) > > For the naming of the DirectRunner, I saw it also, and we should align > the runners naming (we have FlinkPipelineRunner and > SparkPipelineRunner). I sent an e-mail to Davor and Frances to discuss > about that. > > Regards > JB > > On 06/17/2016 09:42 AM, Ismaël Mejía wrote: > > Do we have a list of breaking changes (from the Google Dataflow SDK to > > Beam), because this is going to be important considering other recent > > breaking changes, for example this two that I found yesterday too: > > > > DirectPipelineRunner -> DirectRunner > > DoFnTester.processBatch -> DoFnTester.processBundle (?) > > > > Ismael. > > > > > > > > > > On Fri, Jun 17, 2016 at 9:19 AM, Jean-Baptiste Onofré <[email protected]> > > wrote: > > > >> Hi guys, > >> > >> I tested the latest Beam SNAPSHOT this morning and a code which was > >> working yesterday is not broken with the last changes. > >> > >> I'm using a filter by predicate: > >> > >> .apply("Filtering", Filter.byPredicate(new > >> SerializableFunction<String, Boolean>() { > >> public Boolean apply(String input) { > >> ... > >> })). > >> > >> The filter method has been renamed from byPredicate() to by(). > >> > >> Just to let others know that it can impact their pipelines. > >> > >> Regards > >> JB > >> -- > >> 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 >
