Re: coGroup Iterator NoSuchElement

2015-06-04 Thread Mustafa Elbehery
xt() returns true. > > 2015-06-04 11:18 GMT+02:00 Mustafa Elbehery : > >> Yes, Its working now .. But my assumption is that I want to join >> different datasets on the common key, so it will be normal to have many >> tuples on side, which does not exist on the other side ..

Re: coGroup Iterator NoSuchElement

2015-06-04 Thread Mustafa Elbehery
ways have (at least) one element? > > Fabian > > > 2015-06-04 10:47 GMT+02:00 Mustafa Elbehery : > >> Hi, >> >> >> public static class ComputeStudiesProfile implements CoGroupFunction> StudentInfo, Person> { >> >>Person person; >> >

Re: coGroup Iterator NoSuchElement

2015-06-04 Thread Mustafa Elbehery
hanks! > > On Wed, Jun 3, 2015 at 3:50 PM, Mustafa Elbehery < > elbeherymust...@gmail.com> wrote: > >> Code Snippet :) >> >> DataSet updatedPersonOne = inPerson.coGroup(inStudent) >>.where("name").equalTo("name&

Re: coGroup Iterator NoSuchElement

2015-06-03 Thread Mustafa Elbehery
.where("name").equalTo("name") .with(new ComputeJobsProfile()); updatedPersonTwo.print(); On Wed, Jun 3, 2015 at 3:45 PM, Mustafa Elbehery wrote: > Hi, > > I am trying to write two coGrouprs in sequence on the same ETL .. In use > co

coGroup Iterator NoSuchElement

2015-06-03 Thread Mustafa Elbehery
tasks in Flink. And how to solve this problem ?? Regards. -- Mustafa Elbehery EIT ICT Labs Master School <http://www.masterschool.eitictlabs.eu/home/> +49(0)15750363097 skype: mustafaelbehery87

Re: Informing the runtime about data already repartitioned using "output contracts"

2015-05-29 Thread Mustafa Elbehery
., both >>> inputs must be equally partitioned (same number of partitions, same >>> partitioning function, same location of partitions). Since Flink is >>> dynamically assigning tasks to execution slots, it is not possible to >>> co-locate data that was

Informing the runtime about data already repartitioned using "output contracts"

2015-05-18 Thread Mustafa Elbehery
that the first coGroup result is already partitioned ?! I know I can re-partition again before coGrouping but I would like to know if there is anyway to avoid a step which was already executed, Regards. -- Mustafa Elbehery EIT ICT Labs Master School <http://www.masterschool.eitictlabs.eu/h

Re: CoGgroup Operator Data Sink

2015-04-14 Thread Mustafa Elbehery
2 > > So the output of CoGroup could be Tuple2, when the > integer is 1, it is only written by Sink1, when the integer is 2, its only > written by Sink2. > > > > > On Tue, Apr 14, 2015 at 10:20 AM, Mustafa Elbehery < > elbeherymust...@gmail.com> wrote: >

CoGgroup Operator Data Sink

2015-04-14 Thread Mustafa Elbehery
suggestions, Regards. -- Mustafa Elbehery EIT ICT Labs Master School <http://www.masterschool.eitictlabs.eu/home/> +49(0)15750363097 skype: mustafaelbehery87