Why not? You do data1.join(data2).where(0).equalTo(0).projectFirst(0,1).projectSecond(1).types(Long.class, Long.class, Long.class).flatMap(new MyFM())
The flatMap MyFM function works on Tuple3<Long, Long, Long> and not on a Tuple2<Tuple2<Long,Long>, Tuple2<Long,Long>. 2014-06-18 13:34 GMT+02:00 Ufuk Celebi <[email protected]>: > > On 18 Jun 2014, at 13:30, Robert Metzger <[email protected]> wrote: > > ---------- Forwarded message ---------- > > From: Fabian Hueske <[email protected]> > > Date: Wed, Jun 18, 2014 at 11:20 AM > > Subject: Re: [stratosphere-users] FlatJoin implementation > > To: "[email protected]" < > > [email protected]> > > > > To the topic: This feature has been requested by quite a few people. So I > > think it makes sense to provide this interface (plus joinFilter). The > same > > applies to Cross which is less often used though... > > +1 > > > A less confusing workaround could be to use join.project() an flatMap. > > Do you mean join.project() and flatMap as a workaround for a flatJoin()? > That will not work, will it?
