One part why the tuples are faster is actually the simpler serialization format without null values...
On Wed, Sep 23, 2015 at 5:24 PM, Flavio Pompermaier <pomperma...@okkam.it> wrote: > I could but I heard about the fact that the Tuple model is much faster > than the Pojo one, isn't it? > How big is such difference? Is there any blog post about that? > > Thanks for the support, > Flavio > > On Wed, Sep 23, 2015 at 4:00 PM, Fabian Hueske <fhue...@gmail.com> wrote: > >> Flink's tuple data types do not support null fields. >> A program with null-valued tuple fields will fail as soon as the tuple is >> serialized (written into memory, to disk, or shipped over the network). >> If you need support for null values, you can for example implement a >> custom POJO data type. >> >> Best, Fabian >> >> 2015-09-23 15:34 GMT+02:00 Robert Metzger <rmetz...@apache.org>: >> >>> Are you talking about a Tuple2<String, Boolean> t for example? >>> So t.f0 == null doesn't cause any issues, but t.f1 == null is failing? >>> What's the error message? >>> >>> On Wed, Sep 23, 2015 at 3:31 PM, Flavio Pompermaier < >>> pomperma...@okkam.it> wrote: >>> >>>> Hi to all, >>>> >>>> why it is possible to collect (in a flatMap function for example) a >>>> Tuple with a null String but it's not possible with a null Boolean value? >>>> Is that normal? >>>> >>>> Best, >>>> Flavio >>>> >>> >>> >> > >
